RE: SQL vs native access (was: Record name the same as the filename)

> 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