Runtime Error 3057 in VISTA

I cannot add a WHERE clause to a query in Access 2003 on my VISTA machines.

If I add a new WHERE clause to a SELECT query the query definition will not
be saved.
Any existing query with a clause, when run, returns a runtime error 3057

A table with say RECNAME, RECDATE and RECADDRESS fields will list all
records if I SELECT them.
But if I want say records WHERE RECDATE DATE()-10 then I cannot save the
definition/the query would not run.

I've copied my 2003 database from an XP machine where everything runs fine.

I think I'm also going to have dlookup problems along similar lines ... but
that (may be another thread!)

Any help gratefully received.
Regards,
Dave.

This is certainly not typical behavior for Access 2003 under Vista. Some
questions/suggestions:

Do you have multiple versions of Access on the machine? This can be a
problem under Vista. http://allenbrowne.com/bug-17.html

Have you tried turning off the UAC? That would narrow the problem down to
Vista or Access.

Is it ANY Where clause or just *that* Where clause? Perhaps the Date()
function is the problem. This can indicate a problem with references.
http://allenbrowne.com/ser-38.html

That's all I can think of. If none of that works, perhaps re-installing
Access.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L


"Dave180" wrote in message
...
I cannot add a WHERE clause to a query in Access 2003 on my VISTA machines.

If I add a new WHERE clause to a SELECT query the query definition will
not
be saved.
Any existing query with a clause, when run, returns a runtime error 3057

A table with say RECNAME, RECDATE and RECADDRESS fields will list all
records if I SELECT them.
But if I want say records WHERE RECDATE DATE()-10 then I cannot save the
definition/the query would not run.

I've copied my 2003 database from an XP machine where everything runs
fine.

I think I'm also going to have dlookup problems along similar lines ...
but
that (may be another thread!)

Any help gratefully received.
Regards,
Dave.

Roger,
many thanks for your input - I had a brainwave over this for the last two
days - it is a 3075 err not 3057
I'll re-post under the "correct" title !!
Sorry to waste your time.
"Dave180" wrote:

I cannot add a WHERE clause to a query in Access 2003 on my VISTA machines.

If I add a new WHERE clause to a SELECT query the query definition will not
be saved.
Any existing query with a clause, when run, returns a runtime error 3057

A table with say RECNAME, RECDATE and RECADDRESS fields will list all
records if I SELECT them.
But if I want say records WHERE RECDATE DATE()-10 then I cannot save the
definition/the query would not run.

I've copied my 2003 database from an XP machine where everything runs fine.

I think I'm also going to have dlookup problems along similar lines ... but
that (may be another thread!)

Any help gratefully received.
Regards,
Dave.

But if, by some miracle , you managed to see through my falsehood, then the
answer is No.
This VISTA laptop had Office 2007 installed by default - which I removed,
but I get the same issue on a desktop running VISTA - that I built from
scratch.
So only one instance of Access on each really.
Dave.

"Dave180" wrote:

Roger,
many thanks for your input - I had a brainwave over this for the last two
days - it is a 3075 err not 3057
I'll re-post under the "correct" title !!
Sorry to waste your time.
"Dave180" wrote:

I cannot add a WHERE clause to a query in Access 2003 on my VISTA machines.

If I add a new WHERE clause to a SELECT query the query definition will not
be saved.
Any existing query with a clause, when run, returns a runtime error 3057

A table with say RECNAME, RECDATE and RECADDRESS fields will list all
records if I SELECT them.
But if I want say records WHERE RECDATE DATE()-10 then I cannot save the
definition/the query would not run.

I've copied my 2003 database from an XP machine where everything runs fine.

I think I'm also going to have dlookup problems along similar lines ... but
that (may be another thread!)

Any help gratefully received.
Regards,
Dave.