|
> From: rob@xxxxxxxxx > > Ok, let's say converting from a CHAIN to a SELECT INTO shaved Y seconds > off. I'd say you were making up the data, because CHAINs are always faster that SELECT INTOs. And that's my point. You're making an anecdotal statements using made up information. Why? > However this person decided to stay with the native access anyway. At > which point (X,Y), on which operation, does it become significant enough > to explain that people will stick with what they are familiar with? A single instance with no data doesn't explain ANYTHING, Rob, which is my point. Yes, some people will stick with what they know. At the same time, other people will use whatever is new. Others will use the thing that best pads their resume. While some will try to figure out what's best for the company. So what exactly was your point? If you don't use SQL it's only because you won't change? I think the responsible thing is to change to SQL where it helps your business. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.