[AccessD] ACCESS Left Behind

Mark,

 That would have been nice!  But you can figure it out by turning on ODBC
tracing.

 If you see only a single SQL statement pushed to the server, then your
good.

 If however you see a series of statements while your query is executing,
then JET's handling the execution. 

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Saturday, January 24, 2015 10:44 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] ACCESS Left Behind

Jim - thanks for this, and it makes sense.
However, the BIG PROBLEM that MSFT did not solve:
providing a property in the querydef that indicates ForcedToLocal
processing.
ForcedToLocal=False means the query will truly be processed by SQL Server.

>
>  There's a lot of wiggle room in that question<g>
>
>  When using linked tables, JET will always try to push a query server
> side
> if it can even though it's not a pass-through specifically.  It can't
> do
> that when:
>
> 1. You join to tables from different data sources.
> 2. You use Access or VBA Expressions in the SQL.
> 3. You use JET Specific SQL.
> 4. You use some SQL expressions such as DISTINCT or GROUP BY
>


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com