Problem with Access Database Crashing?

[Advo]

Hi There. Currently at work, we have a database which is used by
multiple users. Its about 24mb and connects to our SQL database, mainly
just use access for the forms and so on. This database front end is
probably used by about 15 employee's and runs from our server, in this
case SRV2.

The problem is, now and again, the access database will die for a user,
i.e. they will try and load the database, and it gives them error
messages saying that it needs to be repaired. If they click yes, then
they still arent allowed to do it.

This is where the pain arises. In order to fix the database, we have to
get everyone off the access database, and then go to our SRV2 server,
load the database, and then repair it.. this is fine and users can then
go back onto the database.

This isnt ideal, and is happening more and more often. Anyone got any
ideas why, or ways to solve this problem?

Thanks

 

[Rick Brandt]

Hi There. Currently at work, we have a database which is used by
multiple users. Its about 24mb and connects to our SQL database,
mainly just use access for the forms and so on. This database front
end is probably used by about 15 employee's and runs from our server,
in this case SRV2.

The problem is, now and again, the access database will die for a
user, i.e. they will try and load the database, and it gives them
error messages saying that it needs to be repaired. If they click
yes, then they still arent allowed to do it.

This is where the pain arises. In order to fix the database, we have
to get everyone off the access database, and then go to our SRV2
server, load the database, and then repair it.. this is fine and
users can then go back onto the database.

This isnt ideal, and is happening more and more often. Anyone got any
ideas why, or ways to solve this problem?

Thanks

Each user should have their own (local) copy of the file. Having multiple users
in the same file causes exactly what you are seeing.

 

[Advo]

Each user should have their own (local) copy of the file. Having multiple users
in the same file causes exactly what you are seeing.

Could that just be fixed then by creating a copy of that main file on
our server, and distributing that to each single user?

 

[Rick Brandt]

Could that just be fixed then by creating a copy of that main file on our
server, and distributing that to each single user?

Sure. You might want to check out the free utility that Tony Toews provides
that would automatically push new updates to each user if you ever update the
file on the server.

 

[Tony Toews]

Could that just be fixed then by creating a copy of that main file on
our server, and distributing that to each single user?

Yes, but that would be network traffic than each user having their own
copy on their hard drive.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

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

 

[dbahooker]

if you didn't rely on a piece of shit database like MDB you woudln't
have a problem with crashing.

if you used Access Data Projects-- aka ADP then you woudln't have to
worry about this trivial stuff

-Aaron