Report runs, but table it references doesn't exist?

[Steve Woodward]

I've been updating an Access application to reference the main data table via
ODBC and a MySQL. All the basic stuff works, but one of the reports has me
scratching my head.

In the existing application, there is a report that runs that references a
table that doesn't exist! How is this possible?

There were a couple of other reports that referenced queries that didn't
exist, but I was able to recreate the queries, but this mirage table has me
scratching my head.

Any ideas? Many thanks, ~Steve

 

[John Spencer]

Lots of ways.

The table did exist but was deleted. Almost nothing you can do in this case
beyond building and populating a new table or finding a backup and restoring
the table..

The table still exists in MySQL but the link to it was deleted in the Access
application.
Possible solution: Relink to the table

Don't know if MySQL supports views, but if it does you might check to see if
the missing "Table" is a view and then set up a link to the view.

The table exists as a local hidden table. In design view select Tools:
Options and on the View Tab show hidden. (In 2007, you will have to do the
same thing, but the steps will be different.)

Are you sure the missing table is a table and not a query?

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

 

[Dale Fye]

another option, besides what John has listed is that the application creates
a temporary table, then deletes it when it isn't needed.

When I do this, I generally create the temp table in a temporary mdb/accdb
file that I create on the fly, then link to that table. Then drop the link
when I'm done with it, and delete the temp mdb/accdb file when done with it.