[AccessD] Help with Query

Gustav Brock Gustav at cactus.dk
Fri Feb 6 02:03:18 CST 2009

Hi John and Mark and Joe

I wonder if it would help to "isolate" the ODBC table in a query and then use this query to join with the local table.
And/or write the criteria to join on from the local table to a temp table at the SQL Server and then join this with the remote table in a view.


>>> jwcolby at colbyconsulting.com 05-02-2009 20:31 >>>
Does anyone know what might be behind this slowness?  I have an Access application that is required 
to link to data from SQL Server, and it is indeed very slow, a source of annoyance to my client.  I 
do have to filter the data, currently using an inner join.  I really do not want to just copy the 
data into a local MDB table though I will if that will help (hadn't thought much about doing that 
till now).

John W. Colby

Rojas, Joe wrote:
> Thanks Mark!
> Your suggestion leaded me to the answer. Not sure why I didn't just
> filter in the query as opposed to linking to a local table.
> Forest from the trees syndrome I guess.
> Joe
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
> Sent: Wednesday, February 04, 2009 1:49 PM
> To: accessd at databaseadvisors.com 
> Subject: Re: [AccessD] Help with Query
> I have the same issue when pulling data via ODBC...I have found it is
> much quicker to NOT join a local table to a linked ODBC...just my
> opinion.  Any reason you can't do the filtering in one SQL
> statement.(see sample below)
> Good Luck,
> Mark A. Matte
> SELECT PUB_JobOper.Company, PUB_JobOper.JobNum, PUB_JobOper.OprSeq,
>  PUB_JobOper.OpCode, PUB_JobOper.SubContract, PUB_JobOper.ActBurCost,
>  PUB_JobOper.ActLabCost
>  FROM PUB_JobOper,PUB_LaborDtl
>  WHERE PUB_JobOper.JobNum=PUB_LaborDtl.JobNum
>  and PUB_JobOper.Company = 'SNB'
>  and ((PUB_LaborDtl.ClockInDate) Between [dteStart] And [dteEnd]);

More information about the AccessD mailing list