there's a registry entry key under DEBUG, called JETSHOWPLAN which
when turned on will create a text file with the jet query optimizer
plan
this will show you what part of a query is [remotely] handled and
what part is handled by JET
the trick is to understand how to build an equivalent sybase query (or
stored procedure) and use a jet passthrough query to execute it on the
server
rasimmonds@hotmail.com (R) wrote in message news:<6e0be8aa.0312050308.5b8d7e03@posting.google. com>...[color=blue]
> Hi
>
> When an Access query is run against an ODBC table, is it possible in
> any way to tell what is passed to the server? I have a remote Sybase
> database linked into Access and the bandwidth is terrible, so I need
> the processing to be done purely on the server. Some simple queries
> run quickly, so the processing is being done on the server. Some
> complex queries with IIf statements etc. are definately not being
> converted to Sybase compatible SQL and I think therefore that Access
> is requesting the entire tables to be sent down the network and Access
> then locally performs the query.
>
> So I would like to be able to tell which queries will be accepted by
> the server and which won't
>
> thanks
> R.[/color]
