Table export error message

[john2thompson]

Hello,

Hopefully someone out there can help me with a problem I am having with an Access 97 table.

I have a database containing a table. I need to copy this table to another database and overwrite the existing table. Both tables have the same name. When I try to SaveAs/Export it I get a warning that this cannot be done because it has a relationship. So, I delete the relations in both the source and destination tables. But then when I try to export I get the folliwing warning message "The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time". Both databases are stored locally and only the source database (the one I am copying from) is open! Also, after I have received this message, the table in the destination that I wanted to overwrite has been removed from the database?!

Please help, I dont have a clue what is going on!?

Cheers,
John

 

[BNPMike]

Trying to slap one table on the top of another sounds a bit brutal to me - call me old fashioned if you like. Why not drop the target table before you bring in its replacement? As that seems to have accidenatlly happenned, can you now import the table ok?

 

[john2thompson]

Have just tried dropping the table with original copies of the database and the error message is still generated. Even if I try to open the table in Access and copy all the rows of data, I still get the same error message!?

Help!

Cheers,
John

 

[BNPMike]

I dunno what the problem is but I'd be inclined to re-boot the operating system to clear any rogue file locks.

 

[john2thompson]

Done that a few times, still to no avail!? Cheers for input.

Anyone else got any suggestions?

cheers,
John

 

[john2thompson]

Hello,

Thought I would let you all know that I have managed to solve the above problem I just described.
It was to do with corruption in one of the fields that caused this error message to appear.
The field in question was a Memo field, and apparently Access 97 has a bit of a problem with this. Simply by deleting the affected rows (or downloading the appropriate patch from Microsoft) whit problem can be solved.

More info here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;182867&Product=acc97

Thanks again for your help.

cheers,
John