Access is awfully slow for _EVERYTHING_. Move to SQL Server / Accsss Data Projects if you really care about performance. I'd even go so far to reccomend that every sproc / view has with WITH (NOLOCK) clause.

With Jet, you don't get that much control over the environment / multi-user concerns.

"a a r o n . k e m p f @gmail.com [MCITP: DBA]" <aaron.kempf (AT) gmail (DOT) com>
wrote

You never tire of trolling and spreading misinformation, do you, Mr. k e m p
f? If what you say is so, why is it that people with real knowledge of
Access with SQL Server "upgrade" warn that, more often than not, it will be
slower after you upgrade to SQL Server until you revise your database
application?

Considering that most of what you "recommend" is wrong, or just something
you heard, or completely inapplicable, I'm sure everyone is going to be
running, not walking, to their SQL Server DB to add that clause. <SNNRRRCH>

With Jet, you do have control. With SQL Server, there's often a DBA between
the user/developer and the server database -- if you are typical of DBAs,
then better that people stick with Jet (though for two versions, now, Jet is
just an alternative; the preferred file-server DB for Access is ACE).

Larry