By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,107 Members | 1,323 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,107 IT Pros & Developers. It's quick & easy.

Table not found message in Access 2002

P: 3
There is the official database db1.mdb and a copy of it called db2.mdb. A query developed in the db2.mdb works. However when it is imported/exported (tried it both ways) back into db1.mdb the following message is displayed:

The Microsoft Jet database engine cannot find the input table or query 'All Records'. Make sure it exists and its name is spelled correctly.

This is driving me nuts. The table in db1.mdb has not changed names, it exists because I can see it, view it etc. I have manually and programmatically compared the SQL query in db2.mdb with the imported one in db1.mdb and they are the same visually.

Has anyone had experience of this(bug)?


Dec 16 '08 #1
Share this Question
Share on Google+
3 Replies

P: 3
Problem fixed and it was due to the way the Name AutoCorrect feature works in Access. I must say never encountered this problem in dbs like Oracle, Ingres, etc.

Basically opening and closing the tables and queries referenced by the imported SQL statement seems to have caused Access to resolve anomalies/conflicts/etc between the imported SQL statement and other existing stored Name Maps.
Dec 16 '08 #2

Expert Mod 10K+
P: 14,534
Sounds about right. I haven't seen this version of it but I know when using nested queries a similar problem occurs. If you open the query in design view then access will rewrite the query syntax in a way it understands but because it doesn't allow for nested queries it makes the query produce an error. You have to open the query again and change the syntax manually then save it and hope you never have to open it in design view again. :D

The joys of working with Access.
Dec 18 '08 #3

P: 3
Yes indeed. The joys of working in Access. Thank-you msquared for mentioning the other pitfall. For interest the SQL query that was imported UNIONed the recordsets of at least 8 INNER JOINed queries.
Dec 18 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.