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

Microsoft Access corruption compact and repair

P: n/a
I have an Access database that needs to be compacted and repaired
almost on a daily basis. It is the front end that needs to be fixed, so
other users cannot get into it when the problem happens. This is
driving me nuts and needs to be resolved.

The database was originally created in 97 and converted to 2002-2003
format. It is split into front-end and back-end. The it is placed in a
network share for multiple user access. There are only about 25 users
that use the db and on average 10 concurrent. I have rebuilt the db by
creating a blank 2002-2003 db and imported the objects. I have disabled
the "AutoCorrect". Open mode is shared. Record locking is "Edited
Record" and "Open databases using record-level locking" is enabled
(checked). I have compiled the code, then "compact/repaired", then
created an mde file.

Is there anything you can tell be that would stop this corruption
problem?

Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Do each of the 25 have a front end on their local machine?
Linked to the back end which is in this network share location?

--

"mr_mach7" <mr******@yahoo.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
I have an Access database that needs to be compacted and repaired
almost on a daily basis. It is the front end that needs to be fixed, so
other users cannot get into it when the problem happens. This is
driving me nuts and needs to be resolved.

The database was originally created in 97 and converted to 2002-2003
format. It is split into front-end and back-end. The it is placed in a
network share for multiple user access. There are only about 25 users
that use the db and on average 10 concurrent. I have rebuilt the db by
creating a blank 2002-2003 db and imported the objects. I have disabled
the "AutoCorrect". Open mode is shared. Record locking is "Edited
Record" and "Open databases using record-level locking" is enabled
(checked). I have compiled the code, then "compact/repaired", then
created an mde file.

Is there anything you can tell be that would stop this corruption
problem?

Nov 13 '05 #2

P: n/a
Firstly, make sure that each user has their own copy of the front end. Do
not allow multiple users to open the same file.

Secondly, there is a bug in A2002 and 2003 that causes Access to crash where
you use subforms. It seems that if the LinkChildFields is an AccessField,
Access can intermittently crash. To stop this, open the subform in design
view, and add a text box to the subform for the foreign key field named in
LinkChildFields.

After that, perform a decompile by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

For further suggestions on preventing corruption, see:
http://allenbrowne.com/ser-25.html
There are several important points there, including making sure that every
user has the same version of msjet40.dll, and not editing running code.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"mr_mach7" <mr******@yahoo.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
I have an Access database that needs to be compacted and repaired
almost on a daily basis. It is the front end that needs to be fixed, so
other users cannot get into it when the problem happens. This is
driving me nuts and needs to be resolved.

The database was originally created in 97 and converted to 2002-2003
format. It is split into front-end and back-end. The it is placed in a
network share for multiple user access. There are only about 25 users
that use the db and on average 10 concurrent. I have rebuilt the db by
creating a blank 2002-2003 db and imported the objects. I have disabled
the "AutoCorrect". Open mode is shared. Record locking is "Edited
Record" and "Open databases using record-level locking" is enabled
(checked). I have compiled the code, then "compact/repaired", then
created an mde file.

Is there anything you can tell be that would stop this corruption
problem?

Nov 13 '05 #3

P: n/a
First off, the front-end is on the network and all users are hitting
the same file. It is not feasable to place the front-end on each
user's pc.

Secondly, Allen, I did come across an earlier posting of yours and
performed all the tips you suggested, included the ideas you posted
here. However, I am still having the problem.

Nov 13 '05 #4

P: n/a
Putting all the users into a single file defeats the purpose.

You're on your own if you take that approach.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"mr_mach7" <mr******@yahoo.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...
First off, the front-end is on the network and all users are hitting
the same file. It is not feasable to place the front-end on each
user's pc.

Secondly, Allen, I did come across an earlier posting of yours and
performed all the tips you suggested, included the ideas you posted
here. However, I am still having the problem.

Nov 13 '05 #5

P: n/a
"mr_mach7" <mr******@yahoo.com> wrote in
news:11*********************@o13g2000cwo.googlegro ups.com:
First off, the front-end is on the network and all users are
hitting the same file. It is not feasable to place the front-end
on each user's pc.


Then it is not possible for you to solve the problem.

Period.

End of statement.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.