Drew Wutka
DWUTKA at Marlow.com
Thu Jul 5 14:54:58 CDT 2007
I've only played around in .Net. Have not really found a use for it yet. Not that it's a bad language or system, it's just that everything I do already has the VB runtimes, and I have so much VB code that I just am sticking with VB 6 for now. So I can't debate what VB.Net can and can't do. As far as Access goes, I haven't been doing Access unbound very often. I usually just use Access as the db. But as far as Access Front Ends go, I'll through in a form or report when I need it for small projects, but if I am going to be building a full blown access front end, I usually am making it unbound, mainly due to limitations on bound objects. Let me explain, most of the Access FE work is stuff I'm doing as side work. At the moment, I only have one person asking for that, and he can do a lot in Access already. So I get the projects that are a little more then 'cookie cutter' style. For instance, the last big one I built was an inventory system. Some of what they needed to do went beyond what bound can do naturally. So instead of trying to cram the bound 'mold' into what they wanted to do, I built the business logic into Class modules. Everything tied in together, so when something was update in one place, the events alerted every affected process. By it's very nature, this type of business layer has to be unbound (because a bound form leaves the business logic out). My point in this, is that it depends on the project goals. Of course, as we all know, our work is a lot like art. Everyone has their own styles and preferred tools. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Thursday, July 05, 2007 12:32 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Performance tips anyone? Drew, >But Access is just as well suited for unbound solutions too. Just as well suited as what? Access is NOT as well suited for unbound as it is for bound. Access just has TONS of features in it directly dependent on bound forms and controls. Unbounders throw all that stuff away; To try and implement that stuff in an unbound solution requires a LOT of custom code. AFAICT most Access "unbounders" make no effort to recreate most of what Access just "gives" us bounders. And Access is certainly NOT as well suited for unbound as VB.Net (or even VB 6), not that I am an expert in .Net yet. But you are talking a whole nother ball game when you talk .Net. So as much as I love ya, I have to disagree with that one. I think you are one of the "been doing Access unbound so long you forgot the pain" folk. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Thursday, July 05, 2007 1:16 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Performance tips anyone? But Access is just as well suited for unbound solutions too. The only exception to that rule is it's goofiness with callback routines. (Can't go into debug if you have a callback routine ANYWHERE. Goes haywire). Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Thursday, July 05, 2007 11:30 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Performance tips anyone? Jim, >You mentioning this will not cause near the stir as it did 10 years ago as most (all?) have now accepted the reality. ;-) LOL, no not quite. Access is a tool built from the ground up for bound. To even discuss unbound for Access NOW, when much more robust unbound tools are available is ... well... kinda silly. Unless of course you have been doing unbound with Access for the last 10 years in which case you have the expertise to do so. Telling the average Access nubee to use Access unbound is IMHO a disservice to the nubee. He might as well just go learn VB.Net. As for me, if I need unbound it will be in VB.Net, NOT in Access (and I am not an Access nubee). The right tool for the job so to speak. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Thursday, July 05, 2007 12:13 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Performance tips anyone? Yes, Drew you have hit on the key to performance... 'unbound'. You mentioning this will not cause near the stir as it did 10 years ago as most (all?) have now accepted the reality. ;-) Jim -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI BusinessSensitve material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.