Re: poor performance on ACCESS 97 client/oracle 7.3 server application

You will always get the worst performance when you access Oracle through MSAccess. This is because everything goes through the Jet engine. This engine translates commands from MSAccess format to ODBC. ODBC then translates the ODBC complient commands to Oracle's OCI format, which then gets executed.

You can save some time by accessing Oracle through RDO or ADO, which avoids the JET engine, but still goes through ODBC. If you are not worried about portability issues, the fastest (and easiest) method is to use Oracle's "Oracle Objects for OLE (oo4o)". This directly creates OCI code. It is also very similiar to DAO, so if you know; that, you shouldn't have any problems.

Rick

Bernd Rosenau <brosenau_at_gss-online.de> wrote in message news:3764e3c9.8131011_at_news.neckar-alb.de...
> Hi,
>
> our ACCESS 97 client/oracle 7.3 application has poor performance
> despite ORACLE running on a powerfull unix machine with lots of memory
> (several hundred MB !)
>
> The machines on the client side are also very well equiped
> (400 MHZ Pentium II machines with 128 MB of RAM)
>
> Very little data is stored in tables (less than 1000 rows in each
> table !!)
>
> Could it be the case that the NETWARE client installed on these
> machines slows database access down ?
>
> We had a simliar effect at a different client where our ACCESS 97 app
> is run with SQL Server at back end.
>
> Many thanks in advance for your help,
>
> Cheers, Bernd.
>
>
>
>
Received on Mon Jun 14 1999 - 13:46:21 CEST