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

Repair database

P: n/a
Hi,
We have not a smallest access database (30 tables, 160 queries,35
forms,40 reports,15 pages) with some links to other databases and some
sql queries from other databases.The databse is not using many
advanced features and there are only about 15 simple macros.

Recently we have a problem with a need to repair database (2 -4 times
a week).
What is even more alarming is that 2 times happend that even after
repair we could not use buttons for forms openning and then we could
not open even forms directly.We had to use backup.

We are quite dependend on this database.

Does anybody know how we should proceed to find out what might be
wrong with the database.I heard something about network speed problem
which might cause it but I don't think it is in our case.

Regards,

Oskar
Nov 12 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Is the database split into two mdb files: one containing only the tables
(the back end, on a shared resource), and the other with all the queries,
forms, reports, etc, and linked tables? Does each user have their own local
copy of the front end?

Are objects (forms, reports, ...) being created/modified/deleted, and the
code changed?

If a split database is corrupting when no object changes are taking place,
there is a problem with the connection to the data. Either the network is
unstable (e.g. bad network card, bad connection, bad hub, or using an
inherently unstable technology such as WiFi), or else a user is crashing out
of Access without closing it properly, or else a machine is crashing
(hardware problem), or the power in your area has problems. Access will
corrupt if a write is not completed and the database closed properly. Other
than this, a database that is not being modified will corrupt very rarely if
at all.

If you are still developing the database objects, the database will corrupt
periodically. If other users are attempting to use the same database file
(unsplit) while objects are being modified it will corrupt constantly.

Hope that helps identify the cause and steps to resolve.

--
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.

"Medved" <os*********@sca.com> wrote in message
news:6b**************************@posting.google.c om...

We have not a smallest access database (30 tables, 160 queries,35
forms,40 reports,15 pages) with some links to other databases and some
sql queries from other databases.The databse is not using many
advanced features and there are only about 15 simple macros.

Recently we have a problem with a need to repair database (2 -4 times
a week).
What is even more alarming is that 2 times happend that even after
repair we could not use buttons for forms openning and then we could
not open even forms directly.We had to use backup.

We are quite dependend on this database.

Does anybody know how we should proceed to find out what might be
wrong with the database.I heard something about network speed problem
which might cause it but I don't think it is in our case.

Regards,

Oskar

Nov 12 '05 #2

P: n/a

Hello Allen,
thank you for taking care for our problem.

As for your questions ,it is the only 1 database (I did not split it to
tables and other stuff).However,partially I have don this for couple of
tables and forms (some people work only with this separate database).
Databases are on the server -and they are accessed from local computers.

Objects are being modified quite a lot and it happened to me that I have
tried to go to design view while someone else was working and vice
versa.In a past we have had some closing problems as well.

However,people take care for the closing in last 2 weeks and also we
take care for working in design.Furthermore network and HW problems are
definitely not the case.

What is confusing to me is the fact that it happened that database
corrupted also in a time when nothing really "dangerous"
(design,closing,network etc.)was happening.

So I am still a bit uncertain about the cause.Our IT specialist suggest
that it must be something else than what we are mentioning here.

Kind regards,

Oskar

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #3

P: n/a
Definately worth ensuring that you have the latest service pack for your
version of Office from support.microsoft.com.

If you are using Access 2000 and later, you could also turn off Name
AutoCorrect, as this can be a source of corruption:
http://allenbrowne.com/bug-03.html

However, I strongly recommend that you split the database, and give everyone
their own front end. It can be in their own workspace on the server if you
do not want the job of updating them on the individual machines. You can
continue to develop the front end with your own local copy. It will corrupt
periodically, and you can repair or restore as necessary while everyone else
keeps working. Once you have an update that you are ready to distribute,
copy it to their workspace. Splitting is essential.

--
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.

"oskar hritz" <os*********@sca.com> wrote in message
news:40***********************@news.frii.net...

Hello Allen,
thank you for taking care for our problem.

As for your questions ,it is the only 1 database (I did not split it to
tables and other stuff).However,partially I have don this for couple of
tables and forms (some people work only with this separate database).
Databases are on the server -and they are accessed from local computers.

Objects are being modified quite a lot and it happened to me that I have
tried to go to design view while someone else was working and vice
versa.In a past we have had some closing problems as well.

However,people take care for the closing in last 2 weeks and also we
take care for working in design.Furthermore network and HW problems are
definitely not the case.

What is confusing to me is the fact that it happened that database
corrupted also in a time when nothing really "dangerous"
(design,closing,network etc.)was happening.

So I am still a bit uncertain about the cause.Our IT specialist suggest
that it must be something else than what we are mentioning here.

Kind regards,

Oskar

Nov 12 '05 #4

P: n/a
os*********@sca.com (Medved) wrote:
We have not a smallest access database (30 tables, 160 queries,35
forms,40 reports,15 pages) with some links to other databases and some
sql queries from other databases.The databse is not using many
advanced features and there are only about 15 simple macros.

Recently we have a problem with a need to repair database (2 -4 times
a week).
What is even more alarming is that 2 times happend that even after
repair we could not use buttons for forms openning and then we could
not open even forms directly.We had to use backup.


I would agree with Allen. With A2000 and newer you are very vulnerable to
corruptions if you are sharing an MDB containing forms, reports and modules among
users.

For other causes of corruption see the Access Corruption FAQ at my website.

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
Nov 12 '05 #5

P: n/a
Have you tried the solution from Trevor? Lots of times access files
can be fixed by importing everything to a new database. Old "junk"
gets deleted and the objects get refreshed.

Good luck,

Mark van Bree
Nov 12 '05 #6

P: n/a
Thank you for the advise.Now I am 100% sure that I will have to split
the database for the front and back end.
I only regret that I did not do it on the very beginning.
Now it will take at least all Saturday.

Oskar
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #7

P: n/a
oskar hritz <os*********@sca.com> wrote:
Thank you for the advise.Now I am 100% sure that I will have to split
the database for the front and back end.
I only regret that I did not do it on the very beginning.
Now it will take at least all Saturday.


No, that shouldn't take that long at all. There is a splitting tool of some sort.

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
Nov 12 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.