Charlotte Foust
cfoust at infostatsystems.com
Thu Dec 2 10:42:54 CST 2004
I work in VB.Net. I don't agree that it fits well in either VB or Access lists because it is quite different from either. On the other hand, I doubt that there are enough of us developing professionally in VB.Net right now to supplant either list, so why not just let it find its own place. If enough .Net questions get posted in either list, we'll know where it belongs. One thing to think about, though, is that database development in VB.Net is just as different from non-database application development as it was in VB6. The database questions will probably always belong in a database list. Charlotte Foust -----Original Message----- From: Bryan Carbonnell [mailto:carbonnb at sympatico.ca] Sent: Thursday, December 02, 2004 2:27 AM To: Access Developers discussion and problemsolving Subject: Re: [AccessD] RE: [Accessed] Please Advise: Should I Buy "MicrosoftVisual Basic.NET Standard 2003 ..." > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Joe Hecht > Sent: Wednesday, December 01, 2004 6:23 PM To: 'Access Developers > Should we make a vb.net list On 1 Dec 2004 at 18:38, Jim Lawrence (AccessD) wrote: > I think .Net will nicely morph into the VB and Accessed lists. > Everything appears to be going that way, application wise. I concur. -- Bryan Carbonnell - carbonnb at sympatico.ca Every time I close the door on reality it comes in through the windows. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com