Database stability/coruption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have created a database for a multi-user environment. It work fine when 1 or 2 people are on it but when three or more logon it always seems to corrupt and give error message (not an access file ... may be damaged....). Can someone explain and guide me on how to resolve this. I need the database to be stable for multiple simultaneous users.

Thanks

Daniel
 
Is the database split into a Frontend/Backend? If so, do you have a copy of
the Frontend on each user's PC or are they all opening the same Frontend on
the server?

You might also take a look at Tony Toews' webpage:
http://www.granite.ab.ca/access/corruptmdbs.htm

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Daniel said:
Hello,

I have created a database for a multi-user environment. It work fine when
Click to expand...
1 or 2 people are on it but when three or more logon it always seems to
corrupt and give error message (not an access file ... may be damaged....).
Can someone explain and guide me on how to resolve this. I need the
database to be stable for multiple simultaneous users.
 
Do you have your database split into a front end /backend application? If not follow the links below courtesy of Tony Toews.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp.htm for more info. See
the Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

If you start having performance issues when you split check out

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

Also courtesy of Tony Toews.

I was directed to these sites and they have worked wonders.

HTH
Tasha
 
I thought I should also point out a few other things about my database in case it might be the cause of my problem(s):

-all the front-ends are on the server currently (this is only temporary and each user will be installing it directly on there PCs... but currently this is not the case ...)
- the front-ends are mdb and not mde (with the new version of my database ... hopefully ready for implementation monday morning... I will be making it into an mde version... but currently this is not the case ....)

Daniel
 
-all the front-ends are on the server currently (this is only temporary
and each user will be installing it directly on there PCs... but currently
this is not the case ...)

Daniel,
If each user is opening a different frontend, although stored on the server,
then is it always the same frontend that is corrupting or do all of them
corrupt when more 3 or more users open the database?
 
Lynn,

I'm affraid you lost me. Could you run that by me one more time.

They each have an individual copy of the same front-end. Each person has a seperate front-end, which is in fact a copy of my master. This way I don't have 10 people loging into 1 front end.

Daniel
 
Daniel said:
They each have an individual copy of the same front-end. Each person has
Click to expand...
a seperate front-end, which is in fact a copy of my master. This way I
don't have 10 people loging into 1 front end.
Daniel
Click to expand...

Ok..that sounds ok. You should as mentioned place the copy of each pc, as
this will reduce network traffic.

So, is it the users front ends that are corrupting, or the back end data
that these front ends link to?

Further, are you talking about a typical stable office lan, or is there any
type of special network connections here (like a lan, or wireless hub stuff,
remote access etc that you are leaving out?).
 
Tasha said:
I was directed to these sites and they have worked wonders.
Click to expand...

Thanks. Comments like yours make the effort worthwhile.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Daniel said:
Hello,

I have created a database for a multi-user environment. It work fine when
Click to expand...
1 or 2 people are on it but when three or more logon it always seems to
corrupt and give error message (not an access file ... may be damaged....).
Can someone explain and guide me on how to resolve this. I need the
database to be stable for multiple simultaneous users.
 
Albert,

It is the back_end of the database that always seems to become corrupted and in need of repairing.

As for the more technicla information pertaining to the structure of the coporate network... I have no clue... I'm not informed if we are on a LAN ... or other type of connection. BUT if this could be the cause of my problem just say the word I will will make the appropriate inquiries as to find out!!! If so, you would need to let me know exactly which questions to ask my IT department.

Thanks,

Daniel
 
The only thing in terms of the network that you might ask is it a wide area
network..and are parts of the internet used to make the connection. (I doubt
this is your case).

The best list of things to check is of cause at Tony's site:
http://www.granite.ab.ca/access/corruptmdbs.htm

Assuming that you do have the system split, and each user has a copy of the
front end on each pc..then I would look at :

1) op locks setting

2) Some users (or a nasy system admin) is killing the ms-access tasks using
the task manager (you can NOT do this!).

So, any kind of users that whack ctrl-alt-del, or a even a system admin that
shuts down the server, but users have files open needs to be check.

You need to inform the server admin people that if users have the file open,
and the admin of the server kills, or cuts those connections, then
corruption will occur.
 
Back
Top