Hello.
We have 2 identical databases that teams use in 2 different locations.
One no problem. The other, every time it is opened, a copy of it appears in
the same folder called 'db1'. then each time it's opened the numbers go up,
db2, db3 etc. When I delete them the number starts from 1 again.
Why is this happening and how do I stop it?
Thank you
J

Make sure all of the users have Delete permission on the folder. Sounds
like the lock file (with the extension .ldb, not .mdb) is not being deleted
at the end of the session as it should be.

By the way, splitting a database is a good idea if you haven't already done
so:
http://allenbrowne.com/ser-01.html

"JB" <somehow@somewhere> wrote in message
news:%(E-Mail Removed)...
> Hello.
> We have 2 identical databases that teams use in 2 different locations.
> One no problem. The other, every time it is opened, a copy of it appears
> in the same folder called 'db1'. then each time it's opened the numbers go
> up, db2, db3 etc. When I delete them the number starts from 1 again.
> Why is this happening and how do I stop it?
> Thank you
> J

Thanks for replying
When you say 'file delete permission', you mean in the folder that the
database is in? I need to check with the IT team as the network security is
a bit OTT.
Also does it compact on closing automatically coz I've only compacted it
twice and the others don't ever.
Also I'm not sure what you meant with 'are they sharing the same file with
other users', isn't that what you can do with Access? Do you mean, when
I've compacted everyone should be out of the file?
J

"Chris O'C via AccessMonster.com" <u29189@uwe> wrote in message
news:8d308e5a62af3@uwe...
> This happens when the user tries to compact the db but can't delete the
> original db file so the newly compacted db file (db2.mdb) can be renamed
> with
> the original db file name. The next time it happens, the newly compacted
> db
> file is named db3.mdb. The next time, db4.mdb and so on.
>
> Find out why the user can't delete the original db file. Don't they have
> file delete permission? Are they sharing the same file with other users
> (really bad idea) when trying to compact it?
>
> Chris
> Microsoft MVP
>
>
> JB wrote:
>
>>We have 2 identical databases that teams use in 2 different locations.
>>One no problem. The other, every time it is opened, a copy of it appears
>>in
>>the same folder called 'db1'. then each time it's opened the numbers go
>>up,
>>db2, db3 etc. When I delete them the number starts from 1 again.
>>Why is this happening and how do I stop it?
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...ccess/200811/1
>

Yes, the folder in which the database resides. I expect that Chris is
correct about you having residue from attempts to compact the database. I
had assumed you were using db1, etc. generically, but now that I think about
it those are the termporary names Access uses when compacting. You can set
a database to compact on close, but you shouldn't. Before compacting it is
best to save the database, for which you would need extra code, at least, if
it is to be done automatically. I'm not sure how to do that.

Regarding sharing the same file, Access can be used with several users
sharing the same file, but that is a leading cause of database corruption.
I have seen shared databases work for years with no apparent problems, while
others become sullen and uncooperative very quickly. It is a risk. That is
why I sent the link to one of many articles about splitting. If you search
groups for information about Access splitting you will get a bunch of hits,
some no doubt with links to more information.

"JB" <somehow@somewhere> wrote in message
news:(E-Mail Removed)...
> Thanks for replying
> When you say 'file delete permission', you mean in the folder that the
> database is in? I need to check with the IT team as the network security
> is a bit OTT.
> Also does it compact on closing automatically coz I've only compacted it
> twice and the others don't ever.
> Also I'm not sure what you meant with 'are they sharing the same file with
> other users', isn't that what you can do with Access? Do you mean, when
> I've compacted everyone should be out of the file?
> J
>
> "Chris O'C via AccessMonster.com" <u29189@uwe> wrote in message
> news:8d308e5a62af3@uwe...
>> This happens when the user tries to compact the db but can't delete the
>> original db file so the newly compacted db file (db2.mdb) can be renamed
>> with
>> the original db file name. The next time it happens, the newly compacted
>> db
>> file is named db3.mdb. The next time, db4.mdb and so on.
>>
>> Find out why the user can't delete the original db file. Don't they have
>> file delete permission? Are they sharing the same file with other users
>> (really bad idea) when trying to compact it?
>>
>> Chris
>> Microsoft MVP
>>
>>
>> JB wrote:
>>
>>>We have 2 identical databases that teams use in 2 different locations.
>>>One no problem. The other, every time it is opened, a copy of it appears
>>>in
>>>the same folder called 'db1'. then each time it's opened the numbers go
>>>up,
>>>db2, db3 etc. When I delete them the number starts from 1 again.
>>>Why is this happening and how do I stop it?
>>
>> --
>> Message posted via AccessMonster.com
>> http://www.accessmonster.com/Uwe/For...ccess/200811/1
>>

Yes the database was set to compact on close. I've taken that off now.
Thanks for the links on the splitting. Very interesting and I've done that
now.
Thanks for all your advice.
J

"BruceM" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes, the folder in which the database resides. I expect that Chris is
> correct about you having residue from attempts to compact the database. I
> had assumed you were using db1, etc. generically, but now that I think
> about it those are the termporary names Access uses when compacting. You
> can set a database to compact on close, but you shouldn't. Before
> compacting it is best to save the database, for which you would need extra
> code, at least, if it is to be done automatically. I'm not sure how to do
> that.
>
> Regarding sharing the same file, Access can be used with several users
> sharing the same file, but that is a leading cause of database corruption.
> I have seen shared databases work for years with no apparent problems,
> while others become sullen and uncooperative very quickly. It is a risk.
> That is why I sent the link to one of many articles about splitting. If
> you search groups for information about Access splitting you will get a
> bunch of hits, some no doubt with links to more information.
>
> "JB" <somehow@somewhere> wrote in message
> news:(E-Mail Removed)...
>> Thanks for replying
>> When you say 'file delete permission', you mean in the folder that the
>> database is in? I need to check with the IT team as the network security
>> is a bit OTT.
>> Also does it compact on closing automatically coz I've only compacted it
>> twice and the others don't ever.
>> Also I'm not sure what you meant with 'are they sharing the same file
>> with other users', isn't that what you can do with Access? Do you mean,
>> when I've compacted everyone should be out of the file?
>> J
>>
>> "Chris O'C via AccessMonster.com" <u29189@uwe> wrote in message
>> news:8d308e5a62af3@uwe...
>>> This happens when the user tries to compact the db but can't delete the
>>> original db file so the newly compacted db file (db2.mdb) can be renamed
>>> with
>>> the original db file name. The next time it happens, the newly
>>> compacted db
>>> file is named db3.mdb. The next time, db4.mdb and so on.
>>>
>>> Find out why the user can't delete the original db file. Don't they
>>> have
>>> file delete permission? Are they sharing the same file with other users
>>> (really bad idea) when trying to compact it?
>>>
>>> Chris
>>> Microsoft MVP
>>>
>>>
>>> JB wrote:
>>>
>>>>We have 2 identical databases that teams use in 2 different locations.
>>>>One no problem. The other, every time it is opened, a copy of it appears
>>>>in
>>>>the same folder called 'db1'. then each time it's opened the numbers go
>>>>up,
>>>>db2, db3 etc. When I delete them the number starts from 1 again.
>>>>Why is this happening and how do I stop it?
>>>
>>> --
>>> Message posted via AccessMonster.com
>>> http://www.accessmonster.com/Uwe/For...ccess/200811/1
>>>
>

It sounds to me like Jet is not reliable enough for you.
I would move to SQL Server if you want a simple environment.

I don't have to worry about compact / repair, I usually setup a
Maintenance Plan Wizard usign SQL Server Agent, and 'it just works'.

ADP is the best frontend for SQL Server, IMHO.

-Aaron



On Nov 14, 11:09*am, "JB" <somehow@somewhere> wrote:
> Hello.
> We have 2 identical databases that teams use in 2 different locations.
> One no problem. The other, every time it is opened, a copy of it appears in
> the same folder called 'db1'. then each time it's opened the numbers go up,
> db2, db3 etc. When I delete them the number starts from 1 again.
> Why is this happening and how do I stop it?
> Thank you
> J