Re: Client Server-How is work shared?

Hi,
The rule is quite simple:
as soon as you use in your Access query a function which is not supported by Oracle, the query will run on the client. So all vb specific functions will cause a performance hog.
This isn't the end of the story: the ODBC is usually very bad at mapping vb and Oracle functions. If it's not a function with the same name, the same parameters and the same syntax: forget it. You can check by enabling trace in the ODBC applet in Control panel. Here you will see which statement is send to the server. We ended up with transforming many of our queries in passthrough queries. And yes, this is server only.
One of my favorite expressions at that time was 'ODBC, weg ermee / throw it away'
If you have the option, you should consider using Oracle Objects for OLE with VB or Vc++, or RDO in VB
All are native drivers, and also bypass the JET-ISAM engine, which ODBC in Access doesn't
I didn't try, BTW, intentionally try to insult Ms-Access users. IMO MS-Access is stil unsuited for mission-critical purposes. I know any end-user will like it. As long as it's standalone on a system not connected to any network, I love it.

Hth,
Sybrand Bakker, Oracle DBA

Brian wrote in message <377246F6.906B6B77_at_techcat.com>...
>Hi.
>We query against ORACLE 7.3.3.6 on AIX 4.1.2 with MS ACCESS7.
>In a regular ACCESS query, when select some records from an attached
>ORACLE table of 3million+ records, how much of the selection is done on
>the server and how much is done by ACCESS? Is there a way to check?
>If we use a SQL PASSTHROUGH query, isn't all of the record selection
>done on the server?
>Thanks!
>brian_at_techcat.com
Received on Thu Jun 24 1999 - 11:52:33 CDT