Jim DeMarco
Jdemarco at hudsonhealthplan.org
Mon Sep 13 08:12:34 CDT 2004
If you're an Access developer and plan on remaining one forever then maybe (and only maybe) you can choose to ignore the .NET platform. There's always talk of a .NET supported Access version so you may well need to look at it at some time. If you're interested in web development than it should not be ignored (and in fact should be considered) and although there are still security issues web services give us a chance to talk to disparate systems and ease creation of distributed applications. There are already hooks into Word and Excel so can Access be far behind? I doubt it (IMHO). Jim DeMarco -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Hewson Sent: Monday, September 13, 2004 8:58 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] MS Access to VB6 or VB.net I'm at #4. I don't have the time nor the inclination to learn it. Jim Hewson -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Monday, September 13, 2004 7:45 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] MS Access to VB6 or VB.net Richard, I think rather then the worrying about the front end, you should be considering the BE and the technology behind it. However without knowing a lot more about your app, it's hard to say if that's critical or not. Also, you didn't mention why you were considering moving from developing the FE in Access itself. As for VB.Net, I've been ignoring it for the most part for some of the same reasons you outline (distribution) plus the fact that it has a large learning curve. I can't see spending the time on that when I already have tools at my disposal that do the job fine. And I'm not the only one. Overall it seems that .Net has been poorly received by the development community. Most developers I know are happy (for the most part) with what they already have/know. Of course a lot depends on the types of apps you develop and the end users you target. I think most of us on this list are on the smaller end of the scale developing typical business type apps for 50 concurrent users or less. How about a quick un-scientific poll? 1. Do you currently develop in .Net (you know it and use it on a regular basis) 2. Are you learning .Net for a project (your just starting out with it and have done a small project or two). 3. Don't know anything about it, but are interested in it. 4. Could care less. I'm firmly at #4 for the moment. Jim Dettman (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Griffiths, Richard Sent: Monday, September 13, 2004 5:20 AM To: AccessD at databaseadvisors.com Subject: [AccessD] MS Access to VB6 or VB.net Hi Group After advice and thoughts. I have a piece of commercial software (library s/ware for schools) written with A97 FE and BE. I am about to rewrite and can't decide over VB6 FE/A2K(DAO) BE or VB.net FE / A2K BE.(reason for change to VB as opposed to MS Access is that the VB footprint will be smaller 1-2mb [easier to email/download and manage than my 12-13 mb Access FE]). On one hand the VB6 route will be quicker to develop (no learning curve) and I think to deploy. On the other hand VB.Net is the future (most likely!!)(and learning and developing in this will be more interesting and will spur me on) but I am concerned (mainly) about deployment as my users are not very IT literate and their pc's (at this time) are not up-to-date (some W95 many W98 32-64mb ram - I know .net is no go on W95). So deployment of .net requires not only the framework but they need minimal Data Access 2.7, IE 5.01, Windows installer etc also installed. But 6-12 months down the line I don't want to be in the posistion that having used VB6 to then consider rewriting in Vb.net. What I can't gauge here is how significant these issues are (and any other issues). So what I am hoping to get here is how you would approach this conundrum - tried and tested VB6 or new VB.net? Thanks Richard -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com *********************************************************************************** "This electronic message is intended to be for the use only of the named recipient, and may contain information from Hudson Health Plan (HHP) that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately, either by contacting the sender at the electronic mail address noted above or calling HHP at (914) 631-1611. If you are not the intended recipient, please do not forward this email to anyone, and delete and destroy all copies of this message. Thank You". ***********************************************************************************