Make-Table Query Destroys the Wrong Table

[Margaret Bartley]

Access 2003.

My make-table query is used to debug a process.

It involves using a Totals query to create a table, then remove a field from
the query grid, changing the name of the output table, and running the query
again, so I can compare the first table with the second table.

What's happening, though, is that it's remembering what the name of the
table was before the query was changed, and replacing the old table with the
new table, even though they have different names.

Arrggh!

Is there any place that talks about these weird anomalous query activities?
I have other examples, but they it's too complicated to talk about on a
newsgroup posting, I'd like to just educate myself a little more on what's
going on.

 

[Jerry Whittle]

Obviously this isn't done with just a single make-table query. What is the
code running this process?

 

[Margaret Bartley]

There is no code. I'm in the user interface, manually running this
MakeTable query, deleting a field from the query, changing the name of the
table and running the query. I was not saving the query between runs, just
clicking the footprint.

After I had run the query five times, systematically removing one field each
time, I went to the Tables list, and discovered that all my first tables had
been deleted, and replaced with the new tables.

I assume if I had forgotten to change the names of the output tables, I
would not see the names of the new tables, just the old ones with the new
data in them.