When you design a client/server application, you can change its performance by adjusting the following settings in the HKEY_LOCAL_MACHINE\SOFTWARE \Microsoft\Office\8.0\Access\Jet\3.5\Engines\ODBC key of the Windows Registry:
TraceSQLMode If queries on remote data are taking too long to complete, set the TraceSQLMode setting to 1 to inspect the SQL statements being sent to the server. If some of the statement’s clauses or restrictions aren’t being sent, you may be using functionality provided by Microsoft Jet but not supported by the server. The SQL statement log is written to the file SQLOut.txt located in the same folder as the currently active .mdb file.
JetTryAuth If your application doesn’t use Microsoft Access security, set the JetTryAuth setting to 0 to prevent Microsoft Access from attempting to log on to the server by using the active user name and password. On some servers, if an attempt to log on fails, it can take time and slow down the server.
PreparedInsert and PreparedUpdate These settings determine whether Microsoft Access inserts or updates data in all fields (including inserting Null values and updating unchanged fields). If you have triggers or defaults on your server tables, don’t set these settings to 1. However, if you don’t have triggers or defaults on your tables, setting the PreparedInsert and PreparedUpdate settings to 1 can marginally speed up insertions and updates.
FastRequery If you use subforms and aren’t concerned about the number of connections you use, you can set the FastRequery setting to 1. This may use more connections, but it marginally improves the speed of subforms and other requerying operations by using prepared SELECT statements with queries that have parameters.
See Also For information on other Windows Registry settings for Microsoft Access, see “Adjusting Windows Registry Settings to Improve Performance” in Chapter 13, “Optimizing Your Application.”