I have an application that sends SQL Insert statements via ODBC into a
MS Access 97 Database (it uses the MS Jet 3.5 driver). The application
is horrible slow (only about 1 insert per second). My suspect is that
the Jet engine does not support prepared Statements by default. In the
jetsql35.hlp file a registry parameter "PreparedInsert" is documented
which is 0 by default. But setting this parameter does not help. I tried
to set the Parameter "TraceSQLMode" but no trace file is written. Am I
looking into the wrong directory? On my Windows NT System I found these
Parameters in the registry under:

HKEY_LOCAL_MACHINE/Software/Microsoft/Jet/3.5/Engines/ODBC

Do you know how to turn on the tracing? Does MS Jet 3.5 support prepared
insert?

Thank you
Stefan

Why are you using ODBC? If you are using ODBC from ADO (Web Page, etc) then
you should upgrade to the OLE DB Provider for Jet.

If you are not using ODBC from a ASP page, etc, the issue may be other
things. Where is the database? Is it on the same machine as the users? How
fast is the network. How many indices do you have. All of these factor in
the picture.

Give us some more info.

--
Stephen Forte
President, NYC Access & VB Developers Group
http://www.nycaccessvb.com
http://www.auroradev.com
-----------------------------------------------------------------

It may be possible to use other DB-interfaces from Microsoft Java. However
until now I'd like to keep with the standard JDBC interface. But obviously
using the standard interface seems to impact the performance too much.

mfg Stefan

Stefan,

If you create a parameterised Insert query in your Access mdb, then you can
treat it as a stored procedure from an ODBC point of view.  Use the ODBC
Call syntax.

Cheers,

Mark Weston
Real Solutions Pty. Ltd.