I have an access 2000 front end pointing to sql server tables (linked tables).

Some reports are using a query like:

SELECT MC_Reception.Reception_Date, Supplier.Supplier
FROM MC_Reception, Supplier
WHERE ((MC_Reception.Supplier_Id)=Supplier.Supplier_Id)
and ((MC_Reception.Reception_Date)>=DLookUp("Date_Star t","Report_Dates","[ID] = 12") And (MC_Reception.Reception_Date)<=DLookUp("Date_Finis h","Report_Dates","[ID] =12"));

This works fine on my local machine. Moving this to the client site (
Access and SQL via ODBC) whenever I go to view this report I now get an error:

'E:\abc\mydb.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the serever on which the file resides.

Where 'E:\abc\mydb.mdb' is the path on my local PC - this error occurs on the clients machine.

What is weird is that I can't see a path setup, and as far as I know there is not one in the entire application. Where does this come from?

Now it gets really weird - if I remove the dlookup lines from the query - it works fine eg.

SELECT MC_Reception.Reception_Date, Supplier.Supplier
FROM MC_Reception, Supplier
WHERE ((MC_Reception.Supplier_Id)=Supplier.Supplier_Id)

As far as I can tell all instances of both access and SQL are the same - access 2000 sp1 and sql 7.0 Also, trying to recreate the query from scratch (ie a new query) on the clients pc gives the same error.

Can anyone help?
Thanks,
--Ian