Importing (Or Exporting!) a Table Problem

[Morris.C]

I'm trying to import the tables from an Access97 database into an
Access2003 version.
Of the twenty or so tables, all but one wants to do what it's told!

I get this 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."

What bloody other user, it's only me and the other database ain't open!
Who's trying to change data? I just want to import the bloody table!

The same damn thing happens if I open the Access97 version and try to
export the tables. And it's the same damn table!!

(I get the same thing when I cut and paste it!)

Any ideas on what's going on?

 

[Allen Browne]

The message probably indicates a corruption in the original database.

Close Access, and check the folder where the database resides.
If you see an ldb file with the same name as you mdb, delete it.
The ldb contains locking info. Access deletes it on termination. On abnormal
termination, it can be left with spurious info.

If that does not solve the problem, try opening the table directly and
scrolling through the records. Chances are you will strike one (or more)
where the row is bad and gives errors. If you can identify the bad records,
you can create a query that avoids them, and export that. Details in thte
3rd symptom in article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

If you don't find a record that's bad, you may be able to copy the entire
table (Ctrl+A, Ctrl+C), paste into a new table in A97, and then export that
table.

 

[Morris.C]

The message probably indicates a corruption in the original database.

Close Access, and check the folder where the database resides.
If you see an ldb file with the same name as you mdb, delete it.
The ldb contains locking info. Access deletes it on termination. On
abnormal termination, it can be left with spurious info.

If that does not solve the problem, try opening the table directly and
scrolling through the records. Chances are you will strike one (or
more) where the row is bad and gives errors. If you can identify the
bad records, you can create a query that avoids them, and export that.
Details in thte 3rd symptom in article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

If you don't find a record that's bad, you may be able to copy the
entire table (Ctrl+A, Ctrl+C), paste into a new table in A97, and then
export that table.

No matter what I do, I can't get this bloody table into the Access2003
version.
I even made a copy of the database and it still tells me that another user
is stopping me from importing/ecporting this one table.
It won't let me cut and paste the data because of the same problem.

 

[Allen Browne]

Is it the whole table?
Are you able to create a query into the table, and read (say) just the first
record? If so, it may be possible to get some of the records via the query.

 

[Morris.C]

Is it the whole table?
Are you able to create a query into the table, and read (say) just the
first record? If so, it may be possible to get some of the records via
the query.

I created and tried to run a Make Table Query, into the same database and
then into another database, and got the same thing!?

A strange question...Could it be the size of the table causing the problem?

 

[Allen Browne]

There is a limit of 2GB on the mdb file.

Unless the database is pushing towards that kind of size, then the size of
the table should not be en issue.

You weren't able to create a query that read just the first record from the
table? Not a Make Table, becuase that causes changes to the database.

 

[Morris.C]

There is a limit of 2GB on the mdb file.

Unless the database is pushing towards that kind of size, then the
size of the table should not be en issue.

You weren't able to create a query that read just the first record
from the table? Not a Make Table, becuase that causes changes to the
database.

Yes, I was able to create a query that reads the first line of the table.

 

[Allen Browne]

Good.

Now change the criteria of the table so it can read more lines. At some
point, it will presumably fail. You may need to scroll to the last record,
or wait until Access displays the record count before the failure occurs.

The goal is to locate the record where the failure occurs, and then set the
criteria to one less than that. You can then export the query, and you have
all the records up to the failure point exported into another table. If
there is only one failure point, you can then set the query to all records
after that, and export those too. In that idea scenario, you lose only the
failed record. In a worse scenario, you still have some of the failed
records.

To locate the failure point, you can probably use the halving technique. Try
half way through the table. If that fails, try half of that, and so on until
you identify the failure point.

HTH

 

[Morris.C]

Yes, I was able to create a query that reads the first line of the
table.

After trying many different ways to get around this problem, I stumbled,
blindly, to a solution. I opened the Access97 version and compressed the
database. It, for some reason, created a new database, good ol'
"db1.mdb". I opened it and there it was... that 'bastard table'.
This I was able to import it into the Access2003 version.
Everything now works fine!

Thanks,

 

[Allen Browne]

That's a great outcome, Morris.

Definately a corruption, so opening in the original version makes sense.

 

[Morris.C]

That's a great outcome, Morris.

Definately a corruption, so opening in the original version makes sense.

Thanks for your help Allen.

And may I say...Go the Saints!!

 

[Allen Browne]

Watch it!
Perth is West Coast Eagles country.

(With apologies to Dockers supporters.)