Corruption and Front and Back end

D

Dj

Hi,

I've been working on a database for about one month and I just rolled it out
to other departments today to start populating it. It wasn't 2 hours lated
that my whole file went corrupt. Reseaching here in the discussion group, I
see NOW that with multiusers, I should have done a front-end/back-end set up.
I had never heard of that before, but I'll be reading up on it this weekend.

My question... The compact and repair database option that the file is
recommending I try isn't working. Is there another shortcut to fixing my
problem or do I have to start from scratch on my whole struction and design?

P.S. I even deleted all of the data from all of the tables and I'm still
getting the error. Thanks for any advice you can give. Dj
 
A

Albert D.Kallal

Anything you do should be done on a copy....

Try creating a blank database, and then try importing everything.....

There is some additional help here

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

Assuming you get your data back, I explain how to setup a spilt system here

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

And, as to why you can't use a wireless network, or any type of WAN with
ms-access, I explain why corruption occurs here

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html
 
J

John Vinson

Hi,

I've been working on a database for about one month and I just rolled it out
to other departments today to start populating it. It wasn't 2 hours lated
that my whole file went corrupt. Reseaching here in the discussion group, I
see NOW that with multiusers, I should have done a front-end/back-end set up.
I had never heard of that before, but I'll be reading up on it this weekend.

My question... The compact and repair database option that the file is
recommending I try isn't working. Is there another shortcut to fixing my
problem or do I have to start from scratch on my whole struction and design?
Click to expand...

Umm...

Backups. Backups. Backups.

They are NOT optional.
P.S. I even deleted all of the data from all of the tables and I'm still
getting the error. Thanks for any advice you can give. Dj
Click to expand...

If you deleted all the data, the data is gone, unless you want to
spring for some fairly expensive database salvage services. If you
Compacted and Repaired after deleting the data, it's REALLY gone -
nobody can ever get it back for you (well, maybe the NSA could, but
then they'd have to kill you).

Sorry you had to learn this lesson the hard way - but if you didn't
back up your database prior to its becoming corrupted, you are very
likely in the situation you describe.

See

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

for some advice on detecting, preventing, and (with all sorts of good
luck) curing database corruption.

John W. Vinson[MVP]
 
T

Tom Wickerath

In addition to the references you've already been given, here is one more
that is certainly worth reading:

Preventing Corruption (Allen Browne)
http://allenbrowne.com/ser-25.html


Also, I have a page of recommendations that you might find helpful:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
D

Dj

After splitting my DB, the corruption is still happening however, I was able
to isolate the corruption to a single user who's using 2003.

I developed the DB using 2002 and all other users are using 2002. As soon
as the 2003 user opens the front-end and tries to open a linked table, her
application locks up and she has to abort out. Then the file has been
corrupted.

I assumed 2003 users can work w/ 2002 developed dbs w/ no problem. Am I
wrong? Do I need to have the 2003 user downgraded to 2002? Thanks again, Dj
 
Top