Simple Import Malfunction

[teel73]

I'm trying to simply import a table from 1 database to another. Both databases reside on my computer's local hard drive. There is no security workgroups attached to either database. The table that I'm trying to import has 80,000 lines (records). My problem is that the import times out and returns the following error 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."

But I have exclusive use to both database because they are on my local drive. I am 100% positive I'm the only one with access to these databases. Also, the database that I'm trying to import from is closed.

I've tried several methods, I've tried linking to the table and making a local copy of it, I tried copying the structure only and then running an append query to get the data into the other database. Each method returns the exact same error.

Can anybody tell me why this is happening and what to do to fix the problem? Could the table be corrupted or is there too much data to perform this action?

 

[gemma-the-husky]

just in case, you only want the "new" database open (you said this was the case)
try doing a compact and repair on both databases before you start

then just import the table from the other database (I dont see why it wouldnt work)

is this a new name, or replacing a similar named table in your database?
also make sure you do not have any timers or any other code runnnig in the new database - just the db window open.

these shouldnt matter, but you never know

--------
note that if the data is linked, rather than intrinsic in the selected database, you will just copy the link


-----------
one other think - close your access, then check task manager just ot make sure there arent any "phantom" access processes running

 

[teel73]

thanks for your help. I figured it out. The stupid database that I was trying to import from was in a read-only state. I found that I when I ran a compact/repair. It compacted it and saved it as db1.mdb then I was able to export the data.... WOW .. Access can be crazy at times.

thanks again