Jet vs ACE

The version of Access where the FE is run would determine that, so it would be the ACE engine. The BE of a split architecture is little more than a text file (assuming an Access BE, of course).

At least that's my assumption.

Thanks Scott
would you know if the format of the 2000 BE is the same as a 2010 BE (if the 2000 one was was updated), and if updating the BE would increase performance? (i.e. does the ACE work better on a newer BE?

cheers.

um...couple of points.

ACE and JET 4.0 are virtually the same.  Outside of a few new data types and a different team taking it over, that's it.

As far as your question:

<<assuming a 2000 BE and a 2010 FE, which engine is in effect? >>

It's more appropriate to ask what code base is in effect, and that would be the version of MSACCESS.EXE that is running.

That code base supports both JET 4.0 and ACE versions.   When the DB is opened, the format is determined and the version, and any version specific rules for that version are followed.

 They are both though fundamentally the same.  JET 3.5 and back were different, but 4.0 and ACE are not.

Jim.

Didn't Microsoft drop the ACE acronym (not 'ace' itself) ?  Access Connectivity Engine ?

<<Didn't Microsoft drop the ACE acronym (not 'ace' itself) ? >>

 Not that I'm aware.

Jim.