[AccessD] Going to vb.net?

We're using Infragistics controls on forms and for subforms (user
control objects in .Net).  We decided on DataDynamics ActiveReports for
reports, since it is very similar to the Access report generator and has
an Access Report wizard that converts the layout for us.  It has some
bugs (like Access doesn't!), but I've found it very easy to work with.
We haven't addressed the issue of charts and graphs yet, but the
ActiveReports tools for those look pretty good as well.

As for doing it from scratch, you don't have much choice in .Net.  Even
if you use custom controls, you have to do the work of deciding how
those controls are going to behave, and there are a plethora of options.
If you've had any experience with VB6 controls, it won't be quite so
confusing, and it's a lot of fun once you get the hang of it.

Charlotte Foust


-----Original Message-----
From: Phil Jewett [mailto:pjewett at bayplace.com] 
Sent: Friday, February 04, 2005 6:00 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Going to vb.net?


Charlotte Foust wrote.... 
 
You could distribute royalty free with the developer edition of Office
too. It's the same thing except they've taken it out of Office entirely.
The runtime package for an Access 2003 app is HUGE. We're switching to
VB.Net for future versions.
 
----------------
I would be interested to know the various 3rd party components you will
be using to replace the functionality of Access (printing reports, data
grids, etc.).  So much of what we take for granted in Access just isn't
built in to vb.net.  Or are you planning on doing it from scratch?
 
Phil Jewett
Phil Jewett Consulting
pjewett at bayplace.com
(619 318-4899
 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com