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" <pfleury@removethissbcglobal.net> wrote in message
news:Xns94709458D71E0pfleuryremovethissbc@128.135. 12.171...[color=blue]
> 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
>[/color]
