Drew Wutka
DWUTKA at Marlow.com
Thu Jul 5 15:05:30 CDT 2007
Huh? You've stepped backwards quite a bit on this ol' buddy. Bound and unbound handle data transfers the exact same way, they are using Jet. There is no need to put in extra locks. In fact, that's one of the main reasons I will go unbound with an app, is if I need to avoid some of the issues involved with a bound application. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Thursday, July 05, 2007 2:06 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Performance tips anyone? I never said anything about hard to use unbound, I said suited to unbound. It plainly is NOT. Access is designed from the ground for bound. It is like taking a Mercedes and yanking the engine out, taking a cutting torch to the frame and trying to stuff a Chevy v8 in it, then splice in all other systems. Yea, it can be done, but it is not "well suited" for that. ANY unbound is harder than bound (regardless of the engine), because you are doing all of the work that the built in "bound code" does for you automatically. You know that Charlotte, you just like to argue. I (bound) do not have to do any locking, etc. You do. And there are TONS of other things that come with the bounded-ness that you either do not provide, or code in all over again. In my personal opinion, it IS hard to use unbound for exactly those reasons. If I wanted to write code to replace the Access bound engine I would not use the Access bound engine!!! At least not if I were starting a project today, July 2007. And of course I do count you in with Drew. Those who have done it so long they forgot the pain. 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 Charlotte Foust Sent: Thursday, July 05, 2007 1:41 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Performance tips anyone? Hey, count me in that group with Drew, John. Access isn't hard to use unbound. You just have to write the same code you would have to write in *any* language to work with unbound objects. The freedom is certainly worth the sacrifice of the bound uh ... "boundaries". Your problem is that it doesn't play nicely with your framework!! Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Thursday, July 05, 2007 10:32 AM 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 -- 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 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.