[AccessD] Going to vb.net?

But VB programmers have grumbled about Access for years, because of the
pre-built functionality.  I like Access, but it's becoming harder and
harder to build industrial strength applications in it, as Microsoft
aims it more and more at power users instead of developers.

Charlotte Foust


-----Original Message-----
From: Boogie Loogie [mailto:boogieloogie at gmail.com] 
Sent: Friday, February 11, 2005 6:57 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Going to vb.net?


On Fri, 4 Feb 2005 17:59:41 -0800, Phil Jewett <pjewett at bayplace.com>
wrote:
> 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

With Access if you want to wring the doorbell you just tell access to
ring the doorbell. In VB.Net you have to explain what a doorbell is, how
it works, where it is, oh it is attached to a house you say? Hmmm what
is a house VB.Net will ask.

Powerful yes, shortcomings Oh yeah but it is a necessary tool of the
trade.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com