By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,139 Members | 1,247 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,139 IT Pros & Developers. It's quick & easy.

database crash

P: n/a
g
Hi,
I have an MS Access 2000 Database on a network. When ever 2 people use it at
the same time it crashes. The database size is 14 megs. I have another
database just like it...and it has not experienced any problems like this.
It is about 5 MB. I don't think that size will matter? Anyhow the crashes
occur usually when someone is using a form, and another person opends up a
database and then in a given ammount of time closes it. Afterwords I
cannot open the database. I was able to fix this with the JetComp tools
though. But it would be nice if these crashed did not occur at all.

Here what happens when I open after a crash:
--I enter database password. The I get a popup message..."The database <file
name> needs to be repaired or isn't a microsoft access databse. Do you want
to repair the database?'
--I click yes. Another pop-up "password not recognized"
--I click ok. Another popup: "The database <filename> can't be repaired or
isn't a MS access database."
--I click ok. Then again I get "not a valid password".
--I click ok...then get grey screen.
I can repair the databse with the JetComp utility, but I would have to use
this every day when it crashes. That is just not an option.

I don't think that one of my modules or forms is interfearing with normal MS
ACCESS opperations? They are just simple dataprocessing functions...

Thanks,
Any help appreciated.

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
First, if I don't misunderstand, you have multiple users logging in to the
same front-end (queries, forms, reports, macros, modules) user interface
database or monolithic (all that plus data). If so, then that alone puts you
at a higher risk for corruption.

There are a number of other problems, and they got worse in the Access 2000
/ Windows 2000 era. The best collection of information and links on avoiding
corruption in a multiuser environment is at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

For a general overview of topics I thought worth discussing with members of
my user group, download the presentation on Access in a Multiuser
Environment from http://appdevissues.tripod.com.

Larry Linson
Microsoft Access MVP
"g" <--*@sdlf.com> wrote in message news:bn**********@mozo.cc.purdue.edu...
Hi,
I have an MS Access 2000 Database on a network. When ever 2 people use it at the same time it crashes. The database size is 14 megs. I have another
database just like it...and it has not experienced any problems like this.
It is about 5 MB. I don't think that size will matter? Anyhow the crashes
occur usually when someone is using a form, and another person opends up a database and then in a given ammount of time closes it. Afterwords I
cannot open the database. I was able to fix this with the JetComp tools
though. But it would be nice if these crashed did not occur at all.

Here what happens when I open after a crash:
--I enter database password. The I get a popup message..."The database <file name> needs to be repaired or isn't a microsoft access databse. Do you want to repair the database?'
--I click yes. Another pop-up "password not recognized"
--I click ok. Another popup: "The database <filename> can't be repaired or
isn't a MS access database."
--I click ok. Then again I get "not a valid password".
--I click ok...then get grey screen.
I can repair the databse with the JetComp utility, but I would have to use
this every day when it crashes. That is just not an option.

I don't think that one of my modules or forms is interfearing with normal MS ACCESS opperations? They are just simple dataprocessing functions...

Thanks,
Any help appreciated.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.