Join Split Database

[Guest]

I need to rejoin a split database. I've removed all the linked tables (4) and
I've imported 3 of the 4 tables from the back end database. Unable to import
the 4th. The message is "The Microsoft Jet dabase engine stopped the process
because you and another user are attempting to change the same data at the
same time." There are no other users while I'm doing this. I'm sure I've
done this before with no problems. Does anyone know what could be going
wrong this time?

Thanks in advance for any help you can offer. This has had be stumped for
days.

 

[Immanuel Sibero]

Hi Katherine,

It's possible the table is corrupted.

- Make a backup of your backend. You should do this on a regular basis
anyway.
- Make sure there is no .ldb file hangin around.
- Compact and Repair the BE. See if this helps.
- If it doesnt, try import just the structure of the table, link to the
problem table and do an "append query" from the problem table.


Another option is export the problem table to a text file first, then read
in the text file.


HTH,
Immanuel Sibero

 

[Jeff Conrad]

in message:

I need to rejoin a split database. I've removed all the linked tables (4) and
I've imported 3 of the 4 tables from the back end database. Unable to import
the 4th. The message is "The Microsoft Jet dabase engine stopped the process
because you and another user are attempting to change the same data at the
same time." There are no other users while I'm doing this. I'm sure I've
done this before with no problems. Does anyone know what could be going
wrong this time?

Thanks in advance for any help you can offer. This has had be stumped for
days.

Hi Katherine,

This could indicate some kind of corruption if you are sure no else is using
the file and there is no LDB file present. The above message is one possible
symptom of corruption:

http://www.granite.ab.ca/access/corruption/symptoms.htm

See if these links on corruption help.

http://allenbrowne.com.au/ser-47.html

http://www.granite.ab.ca/access/corruptmdbs.htm

http://www.rogersaccesslibrary.com/OtherLibraries.asp#Whittle,Jerry
(See Fix Corrupt Access Database v3.9 Document)

http://www.e-tech.ca/001-AccessFAQ.asp

http://www.everythingaccess.com/tutorials.asp?ID=0

ACC2000: How to Recover Data from a Corrupted Table by Using the DAO Method
http://support.microsoft.com/?id=815280

ACC2000: How to Troubleshoot Corruption in a Microsoft Access Database
http://support.microsoft.com/?id=306204

ACC2000: How to Troubleshoot and Repair a Damaged Jet 4.0 Database
http://support.microsoft.com/?id=209137

ACC2000: How to Recover Data from a Damaged (Corrupted) Table
http://support.microsoft.com/?id=247771

ACC2000: How to Use MS Query to Recover Data from a Damaged Jet 4.0 Database
http://support.microsoft.com/?id=304561

Jetcomp utility available at:
http://support.microsoft.com/?id=273956

Good luck,

 

[Guest]

Thanks for responding, Jeff. I scrolled through the table and found a record
with #ERROR in the memo field. I deleted the record and did a
compact/repair. Now when I try to import the table I get a 'Record is
deleted' error (Error 3167). I scrolled through the table again and found a
different record with #DELETED in the memo field. I've deleted that record
and I'm reading from the links you directed me to to try and find a solution.
My understanding of access is limited so a lot of this may be over my head.
Am I on the right track so far?

 

[Jeff Conrad]

in message:

Thanks for responding, Jeff. I scrolled through the table and found a record
with #ERROR in the memo field. I deleted the record and did a
compact/repair. Now when I try to import the table I get a 'Record is
deleted' error (Error 3167). I scrolled through the table again and found a
different record with #DELETED in the memo field. I've deleted that record
and I'm reading from the links you directed me to to try and find a solution.
My understanding of access is limited so a lot of this may be over my head.
Am I on the right track so far?

All of the links I provided should be reviewed at this point Katherine since
there is without question some corruption in this table. Make some backups
of this database immediately and use the techniques in the links on those
backups just in case something blows up.

I would start here first:

Jetcomp utility available at:
http://support.microsoft.com/?id=273956

 

[Guest]

Wow - that was a quick response. Thanks so much. Sorry if this is a stupid
question - and I'm not even sure how to ask it - but is it the front end or
back end that I'm attempting to fix? I know the tables are in the back end
but isn't it the front end that I compact & repair? If all goes well and I'm
able to recover the corrputed db/table, should I have the users replace their
copies of the front end or is it sufficient that the table is repaired in the
back end?

 

[Jeff Conrad]

in message:

Wow - that was a quick response. Thanks so much. Sorry if this is a stupid
question - and I'm not even sure how to ask it - but is it the front end or
back end that I'm attempting to fix? I know the tables are in the back end
but isn't it the front end that I compact & repair? If all goes well and I'm
able to recover the corrupted db/table, should I have the users replace their
copies of the front end or is it sufficient that the table is repaired in the
back end?

If all your tables are in the back end (this should be the case in most situations)
then it is the back-end we need to work on. The front end merely has links
to the data tables and so anything you attempt to implement on the front end
will not solve the corruption issue. The users *should* not need to do anything
with their front ends when everything is fixed. However, no harm will be done
by giving them a fresh FE copy either once the issue is resolved.

Since other users are using this database this is what I would do:
1. Have everyone completely log out of the FE databases.
2. Double check through Explorer that the location of the BE does
not have any residual LDB (locking file) present.
3. Make two copies of the BE file and place in separate folders on
your C drive so you can work on it without interruption.
4. Best case scenario is the users will not need to use the database
when you are fixing it. If they *have* to use it, instruct them that
any changes they make between now and when it is fixed will be
lost. Tell them to keep a record of the changes they make so they
can re-do the changes when everything is working OK.
5. Download and follow the instructions here:

Jetcomp utility available at:
http://support.microsoft.com/?id=273956

6. If everything *appears* to be OK, test, test, and test some more.
7. Create a new blank database, turn off Name AutoCorrect, and then
attempt to import all the data tables from the *fixed* file into this new
container. If all the tables come across OK then I think you should be
in good shape.
8. Go back to the shared folder where the BE is placed on the server.
Delete the existing file. Make sure there is no locking file present. Tell
everyone to close everything.
9. Copy your *fixed* BE into this shared folder. Hopefully everything
should be working again.
10. Create two new folders on the server somewhere where you can
find them. Name them CorruptedBEFile1 and CorruptedBEFile2.
(Two is better than one)
11. Take one of the copies of the old corrupted BE file and place a
copy in each of these folders. Rename the database file to:
CorruptedBEMay262005.mdb in each of the folders
12. Place a copy of the *fixed* file as well into a new folder on the
server (FixedBEFile) and name it FixedBEMay262005.mdb.

Hopefully you should be OK now.
Review the links I provided before as well because some of them
discuss ways to prevent corruption. Very important reading.

 

[Guest]

I followed your instructions and everything appears to be just fine now.
Thanks.
But I have problem with a different db now. I tried to compact and repair
the back end of this other db, and I'm getting the message "Microsoft Office
Access has encountered a problem and needs to close. We are sorry for the
inconvenience." So I've fixed one db, but messed up another. Can you direct
me to a solution to this new problem?

 

[Guest]

Correction - I was able to compact and repair; it was when I tried to import
the tables that I got the message.

 

[Jeff Conrad]

in message:

Correction - I was able to compact and repair; it was when I tried to import
the tables that I got the message.

Hi Katherine,

I would follow the same steps I provided before on this different database.
Try the Jetcomp utility first on a backup copy.

The links I provided also discussed ways of preventing corruption as
well as ways to track down if a particular machine was causing the
problem. I implore you to really, really, read all the information I
previously provided. Also, go to Office Update on *every* workstation
and make sure each computer has all the latest service packs and
updates.

 

[Guest]

You know - I think I'm just tired. But I finally got it. I couldn't have
done it without your help. And thanks too for all the links on preventing
corruption. I've read a lot of it and I'm sure I'll have questions on some
of it. Thanks!

 

[Jeff Conrad]

in message:

You know - I think I'm just tired. But I finally got it. I couldn't have
done it without your help. And thanks too for all the links on preventing
corruption. I've read a lot of it and I'm sure I'll have questions on some
of it. Thanks!

Whew! That is good news Katherine!
I can sleep tonight then.

Definitely a good idea to read all the corruption information. Having this
many corrupt databases should really be raising a red flag. Taking some
time to track down what could be causing the problem(s) may actually
save time (and headaches) later. Even flaky network cards can be an issue
so you may need to check with your Network Admin.

You're welcome for the help, I'm glad I could be of service.