ACC: TransferDatabase Macro Action Does Not Replace Table (106187)
The information in this article applies to:
- Microsoft Access 1.0
- Microsoft Access 1.1
- Microsoft Access 2.0
- Microsoft Access for Windows 95 7.0
This article was previously published under Q106187
Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
If you use a TransferDatabase macro action to transfer a table with the
same name as an existing table in the destination database, the existing
table will not be overwritten by the transferred table.
CAUSE
If the destination database contains a table with the same name as the
table you are trying to transfer, Microsoft Access will give the
transferred table a new name in the destination database. The new name will
consist of the original table name plus a sequential number. For example,
if you try to transfer a table named Categories to a database that already
has a table with the same name, the newly transferred table will be named
Categories1.
RESOLUTION
If you want to replace an existing table using a TransferDatabase macro
action, you first need to rename or delete the existing table in the
destination database.
STATUS
This behavior no longer occurs in Microsoft Access 97.
REFERENCES
For more information about the TransferDatabase action, search the Help
Index for "TransferDatabase action."
Modification Type: | Major | Last Reviewed: | 5/6/2003 |
---|
Keywords: | kbfix kbprb kbusage KB106187 |
---|
|