Access DB 2002 Corrupting database file

supportt

Registered User.
Local time
Today, 04:22
Joined
Nov 21, 2001
Messages
70
I am trying to trouble-shoot an issue with a Access 2002 database. Basically I have the database file shared out on a local network and there are 4 users accessing it. Well, there are using Access 2003 when opening the db file, but every time they exit the db, it is getting corrupted beyond repair.

Any suggestions?

Could it be a version issue? Since I developed it in Access 2002 and they are accessing with a Client 2003ver?

thanks

:confused:
 
If you fix it, then have just one person open and close it, does it still zonk out?
 
Reply for single user

The original setup was just one pc and I did not see any problems at all....
 
Are you putting the frontend on the client(s) and the backend on the server?
 
Reply for setup

The mdb file is on the server and it is shared out to the network users. It is just a shortcut pointing to the mdb file.

thanks
 
Have you tried the frontend / backend setup? While it may not fix this problem, I would suggest it...
 
Reply

Are you referring to splitting the database, if so? I did that and still had the problem...any thoughts on the version differences?

Thanks
 
Hum... I wouldn't think there'd be a problem. I think the next thing I would try is:

1. See if you can make it zonk at your will. Like open it on workstation 1 and then on workstation 2. Then close one and see if you can make it zonk. Then try it on a seperate set of workstations. If it always happens, then you've eliminated a good bit. If not, it may be a particular workstation...

2. Check all your references on each workstation

3. Compile each module of code, one at a time on several diffierent workstations - It may be a simple code sytax error...

4. See if you may have a bad record in the tables by manually scrolling trough the main tables and looking for odd looking charactors.

Hope something here helps... :)

Edit: What part of town are you in?
 
Last edited:
PMFJI but *all* of your users should have their own copy of the FrontEnd preferably on their own local machine. Just making sure that base is covered.
 
Reply

Yes, users do have there own copy of the front-end from the split. I will check the tables to see if there is any bad records. But, I don't think that will be it, because every time the db gets corrupt, I just replace with a fresh copy. This is a new db, so there really is no records in place, starting from scratch...

thanks
 

Users who are viewing this thread

Back
Top Bottom