Query reverts to previous version?!?!

  • Thread starter Thread starter dofnup
  • Start date Start date
D

dofnup

This is the weirdest. It seems my database is haunted!!

I got an Access2000 database/program to work with. There
was a table called [WO] (Work Orders) which had to be
modified. We renamed it to [ALL WO] and changed the
queries that used to refer to [WO] to [ALL WO]. Or so we
thought. During execution, it started showing errors.

I went back and opened a query that I already updated to
[ALL WO.*], and I got an error, saying Microsoft Jet
didn't recognize [WO.*] as a valid field name or
expression. So I open the design, change it to [ALL WO.*]
and save. Then I open a child query and ... get the same
error. I change and save that one, go back to the
parent ... and the parent is back to [WO.*] !!!

Sometimes the queries will revert to [WO.*] even if all I
do is import some new data. I am at my wit's end!!
Whatever I do, somehow the queries "magically" revert to
[WO.*] .... help? Please?
 
I suspect Access sees ALL WO as being the SQL keyword ALL followed by the
table name. Try renaming the table to avoid such possible confusion.

HTH
Sam
 
Dear Dofnup:

I suspect Sam has a good idea in not putting reserved words in table
names, but IF you put the table name in brackets it will work anyway.
However, there's another problem. You DIDN'T put the table name in
brackets, although it looks like you started to do so.

Please try [ALL WO].* instead of [ALL WO.*]. This makes a huge
difference.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

I suspect Access sees ALL WO as being the SQL keyword ALL followed by the
table name. Try renaming the table to avoid such possible confusion.

HTH
Sam
dofnup said:
This is the weirdest. It seems my database is haunted!!

I got an Access2000 database/program to work with. There
was a table called [WO] (Work Orders) which had to be
modified. We renamed it to [ALL WO] and changed the
queries that used to refer to [WO] to [ALL WO]. Or so we
thought. During execution, it started showing errors.

I went back and opened a query that I already updated to
[ALL WO.*], and I got an error, saying Microsoft Jet
didn't recognize [WO.*] as a valid field name or
expression. So I open the design, change it to [ALL WO.*]
and save. Then I open a child query and ... get the same
error. I change and save that one, go back to the
parent ... and the parent is back to [WO.*] !!!

Sometimes the queries will revert to [WO.*] even if all I
do is import some new data. I am at my wit's end!!
Whatever I do, somehow the queries "magically" revert to
[WO.*] .... help? Please?
Click to expand...
Click to expand...
 
Back
Top