Hi,
I have (1) a crosstab query which takes a parameter from a form dropdown, (2) a make-table query based on query 1, which puts the results into a simple table and (3) a report based on the table
When I change the selection in the dropdown and run the make-table query, I get the standard warning that says "You are about to run a make-table query that will modify data in your table". But when I click Yes, it then tells me "Table 'MyTable' already exists.
Shouldn't a make-table query warn me that my table is about to be deleted? Help tells me this:
But this isn't a multiuser database. Although this database does have some back-end tables in common with other databases, this isn't one of them and I'm the only person using this particular front-end.
It's not a big deal as I can manually delete the table and then everything works fine. I just wonder why it behaves like this.
Thanks
Pat
I have (1) a crosstab query which takes a parameter from a form dropdown, (2) a make-table query based on query 1, which puts the results into a simple table and (3) a report based on the table
When I change the selection in the dropdown and run the make-table query, I get the standard warning that says "You are about to run a make-table query that will modify data in your table". But when I click Yes, it then tells me "Table 'MyTable' already exists.
Shouldn't a make-table query warn me that my table is about to be deleted? Help tells me this:
Table <name> already exists. (Error 3010)
You tried to create or rename a table with a name that already exists in this database. Choose another name, and then try the operation again.
In a multiuser database, this error can also occur if you delete a table, another user creates a table with the same name, and then you try to roll back the deletion of your table. To restore your table, the other user must first delete or rename the new table before you try the rollback operation again.
But this isn't a multiuser database. Although this database does have some back-end tables in common with other databases, this isn't one of them and I'm the only person using this particular front-end.
It's not a big deal as I can manually delete the table and then everything works fine. I just wonder why it behaves like this.
Thanks
Pat