Frequent repair messages

[Patrick Fleury]

We have an Access 2002 database and it has started giving us fits.

It works over a network and usually it has several people using it. This
has not been a problem in the past. However, now, when some people try
to log on, a message pops up telling them that this is not an Access
database or that it needs to be repaired. Sometimes, they get a message
telling them that the database is opened exclusivley by another user. In
each of these cases, I go to the server, kick everybody off and then
compact it. Everything goes well for a day or two and then we start
getting messages.

This is a large database - about 70 megabtes - but it is compacted once a
week and I can't believe it needs to be compacted everyday or even twice
a day.

One of our guesses is that printing large numbers of reports from it does
something goofy but we don't know what.

So, what do you think can be going on?

Do I have permissions set wrong? Is there some sort of network security
set wrong? Could there be aproble with the server?

Any and all suggestions appreciated.

--PatF

[Bruce Pick]

I can't tell you the specific cause of the problem. However, a good general
practice
with multiple users is to use a front end/back end configuration, with each
user
having a front end "database" on their own pc. I have "database" in quotes
because
these have no actual data tables, only linked tables which tap into the
back end database tables. The front ends each have a complete set of
queries, forms, reports, and modules as needed for that user.

Bruce Pick

"Patrick Fleury" <pf*****@removethissbcglobal.net> wrote in message
news:Xn**********************************@128.135. 12.171...

We have an Access 2002 database and it has started giving us fits.

It works over a network and usually it has several people using it. This
has not been a problem in the past. However, now, when some people try
to log on, a message pops up telling them that this is not an Access
database or that it needs to be repaired. Sometimes, they get a message
telling them that the database is opened exclusivley by another user. In
each of these cases, I go to the server, kick everybody off and then
compact it. Everything goes well for a day or two and then we start
getting messages.

This is a large database - about 70 megabtes - but it is compacted once a
week and I can't believe it needs to be compacted everyday or even twice
a day.

One of our guesses is that printing large numbers of reports from it does
something goofy but we don't know what.

So, what do you think can be going on?

Do I have permissions set wrong? Is there some sort of network security
set wrong? Could there be aproble with the server?

Any and all suggestions appreciated.

--PatF

[Tony Toews]

Patrick Fleury <pf*****@removethissbcglobal.net> wrote:

Sometimes, they get a message
telling them that the database is opened exclusivley by another user.
Ah, as Bruce states it needs splitting.
This is a large database - about 70 megabtes - but it is compacted once a
week and I can't believe it needs to be compacted everyday or even twice
a day.
Actually my clients frequently don't compact for weeks on ends.
Do I have permissions set wrong? Is there some sort of network security
set wrong?
No and no.
Could there be aproble with the server?

Definitely. But as Bruce mentions, if not already split then you really want to
split the MDB into a FE/BE.

See the Access Corruption FAQ at my website for much more information on corruption
causes and solutions including a link to article explaining splitting in more detail.

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