Re: HELP!! ACCESS ODBC ORACLE

gbray1_at_abacus.tis.tandy.com (Geoff Bray) wrote:
><Stuff deleted>
>
>|> Just remember, Microsoft Access is *NOT* a client/server tool. You can
>

[ stuff deleted about braindead joins]

>Is this just true of MS Access because I'm using Andyne GQL via ODBC to a remote
>dtabase and the join happens on the remote database.
>

This is a function of Microsoft's "jet" engine which is the underlying kernal for Access. You get the same problems if you use the "built-ins" in Visual Basic because you're really using the "jet" engine to do the work.

This is why many people complain about ODBC being slow: what's really happening is that they are using ODBC *through the "jet" engine* (without knowing it) and seeing the behavior described earlier.

GQL should probably be fine unless it also uses the "jet" engine (I'm not a GQL user).

--
Bill Meahan,  Senior Developer  |        wmeahan_at_ef0424.efhd.ford.com
Electrical & Fuel Handling Division, Ford Motor Company
Opions expressed herein are those of the author and in no way represent
any official statement or opinion of Ford Motor Company