I have a database on what we call a server in our office. A number of people
have shortcuts to it. The database is not split, so does not have a backend.
The problem I'm having is that the database seems to be randomly creating
copies of itself and naming them db1, db2, etc. I say randomly, because I've
not been able to determine what 'event' causes a copy to be made. I don't
think it happens everytime the database is opened or changed, but I'm not
sure.

This occured a number of months ago, and I posted to this newsgroup. Someone
was kind enough to suggest I turn off Compact on Close. I did so, and the
problem went away for some time, but has now re-appeared. Maybe I have to
disable Compact on Close in tandem with something else? Maybe it's something
else altogether? Not sure where to go with this one, sure could use some
suggestions.

Ivor

don't use MDB find someone that can move your DATA to SQL Server.

MDB is completely obsolete; but you can still reuse your existing forms
and reports if you simply use Access Data Projects

-Aaron





Ivor Williams wrote:
> I have a database on what we call a server in our office. A number of people
> have shortcuts to it. The database is not split, so does not have a backend.
> The problem I'm having is that the database seems to be randomly creating
> copies of itself and naming them db1, db2, etc. I say randomly, because I've
> not been able to determine what 'event' causes a copy to be made. I don't
> think it happens everytime the database is opened or changed, but I'm not
> sure.
>
> This occured a number of months ago, and I posted to this newsgroup. Someone
> was kind enough to suggest I turn off Compact on Close. I did so, and the
> problem went away for some time, but has now re-appeared. Maybe I have to
> disable Compact on Close in tandem with something else? Maybe it's something
> else altogether? Not sure where to go with this one, sure could use some
> suggestions.
>
> Ivor

Hi Ivor,

You need to split your database into a front end and back end, and give each
user their own copy of the front end to run on their PC's that is linked to
the back end (data) on the server.

This should alleviate the issue for you. It's most likely caused by the DB
attempting to compact/repair itself and being unable to replace the database
with the temp one (db1, db2 etc) as another user has the DB open.

Hope this helps.

Damian.

"Ivor Williams" wrote:

> I have a database on what we call a server in our office. A number of people
> have shortcuts to it. The database is not split, so does not have a backend.
> The problem I'm having is that the database seems to be randomly creating
> copies of itself and naming them db1, db2, etc. I say randomly, because I've
> not been able to determine what 'event' causes a copy to be made. I don't
> think it happens everytime the database is opened or changed, but I'm not
> sure.
>
> This occured a number of months ago, and I posted to this newsgroup. Someone
> was kind enough to suggest I turn off Compact on Close. I did so, and the
> problem went away for some time, but has now re-appeared. Maybe I have to
> disable Compact on Close in tandem with something else? Maybe it's something
> else altogether? Not sure where to go with this one, sure could use some
> suggestions.
>
> Ivor
>
>
>

it's hard to believe that you posted a description of a multi-user
monolithic database in these ngs before, without getting a dozen responses
recommending in no uncertain terms that you split your database. just in
case you didn't, or just in case nobody already posted the following link to
you, here it is:

http://www.granite.ab.ca/access/splitapp/why.htm

hth


"Ivor Williams" <(E-Mail Removed)> wrote in message
news:nFodh.433166$R63.116103@pd7urf1no...
> I have a database on what we call a server in our office. A number of
people
> have shortcuts to it. The database is not split, so does not have a
backend.
> The problem I'm having is that the database seems to be randomly creating
> copies of itself and naming them db1, db2, etc. I say randomly, because
I've
> not been able to determine what 'event' causes a copy to be made. I don't
> think it happens everytime the database is opened or changed, but I'm not
> sure.
>
> This occured a number of months ago, and I posted to this newsgroup.
Someone
> was kind enough to suggest I turn off Compact on Close. I did so, and the
> problem went away for some time, but has now re-appeared. Maybe I have to
> disable Compact on Close in tandem with something else? Maybe it's
something
> else altogether? Not sure where to go with this one, sure could use some
> suggestions.
>
> Ivor
>
>

(E-Mail Removed) wrote:
> don't use MDB find someone that can move your DATA to SQL Server.

Thanks again for your one line answer to everything in life.

--
Joseph Meehan

Dia 's Muire duit

Ivor Williams wrote:
> I have a database on what we call a server in our office. A number of
> people have shortcuts to it. The database is not split, so does not
> have a backend. The problem I'm having is that the database seems to
> be randomly creating copies of itself and naming them db1, db2, etc.
> I say randomly, because I've not been able to determine what 'event'
> causes a copy to be made. I don't think it happens everytime the
> database is opened or changed, but I'm not sure.
>
> This occured a number of months ago, and I posted to this newsgroup.
> Someone was kind enough to suggest I turn off Compact on Close. I did
> so, and the problem went away for some time, but has now re-appeared.
> Maybe I have to disable Compact on Close in tandem with something
> else? Maybe it's something else altogether? Not sure where to go with
> this one, sure could use some suggestions.
>
> Ivor

The one true answer (sounds religious doesn't it?) Is to split the
database.


--
Joseph Meehan

Dia 's Muire duit

The reason it started up again is probably because one of your users turned
Compact On Close back on. The option is machine-specific and not
database-specific.

As others have mentioned, the best solution is to split the database and put
the Front-End on each workstation. However, if that is not possible for
some reason, another alternative is to programmatically turn off the user's
Compact On Close when they open the database.

All you need to do is put:
Application.SetOption "Auto Compact", False
in the On Open event of the first form that opens when you open the database
(you DO have an opening form, don't you?). That's all it takes. Even if
they turn the option back on, the next time they open the database, it will
get turned off again.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L



"Ivor Williams" <(E-Mail Removed)> wrote in message
news:nFodh.433166$R63.116103@pd7urf1no...
> I have a database on what we call a server in our office. A number of
people
> have shortcuts to it. The database is not split, so does not have a
backend.
> The problem I'm having is that the database seems to be randomly creating
> copies of itself and naming them db1, db2, etc. I say randomly, because
I've
> not been able to determine what 'event' causes a copy to be made. I don't
> think it happens everytime the database is opened or changed, but I'm not
> sure.
>
> This occured a number of months ago, and I posted to this newsgroup.
Someone
> was kind enough to suggest I turn off Compact on Close. I did so, and the
> problem went away for some time, but has now re-appeared. Maybe I have to
> disable Compact on Close in tandem with something else? Maybe it's
something
> else altogether? Not sure where to go with this one, sure could use some
> suggestions.
>
> Ivor
>
>

these people don't know what they're talking about.

splitting a database doesn't solve the problem; long term.

moving to Access Data Projects _DOES_ solve this problem

-Aaron


Ivor Williams wrote:
> I have a database on what we call a server in our office. A number of people
> have shortcuts to it. The database is not split, so does not have a backend.
> The problem I'm having is that the database seems to be randomly creating
> copies of itself and naming them db1, db2, etc. I say randomly, because I've
> not been able to determine what 'event' causes a copy to be made. I don't
> think it happens everytime the database is opened or changed, but I'm not
> sure.
>
> This occured a number of months ago, and I posted to this newsgroup. Someone
> was kind enough to suggest I turn off Compact on Close. I did so, and the
> problem went away for some time, but has now re-appeared. Maybe I have to
> disable Compact on Close in tandem with something else? Maybe it's something
> else altogether? Not sure where to go with this one, sure could use some
> suggestions.
>
> Ivor