I have a Database that was created in Access 2000. This Database is access
by several users theouth a network. What happens is that for some unknow
reason to me the Database will brop its name and be renamed db1. Then what
happens is that the users cannot access it through its regular shortcut.
Example. The database name is "TravelInvoiceInvoicing" Then for some reason
when the other users close the program it seems to drop the Name and it
becomes "db1". What causes this and how can we prevent it from happening?

Sounds as though you haven't split the application into a front-end database
(containing the queries, forms, reports, macros and modules), linked to a
back-end databases (containing the tables and relationships). Only the
back-end should be on the server: each user should have his/her own copy of
the front-end, ideally on his/her hard drive.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"sandrao" <(E-Mail Removed)> wrote in message
news:5C4B7728-9119-4E0F-A933-(E-Mail Removed)...
>I have a Database that was created in Access 2000. This Database is access
> by several users theouth a network. What happens is that for some unknow
> reason to me the Database will brop its name and be renamed db1. Then
> what
> happens is that the users cannot access it through its regular shortcut.
> Example. The database name is "TravelInvoiceInvoicing" Then for some
> reason
> when the other users close the program it seems to drop the Name and it
> becomes "db1". What causes this and how can we prevent it from happening?

Would splitting the Database eliminate the problem?

"Douglas J. Steele" wrote:

> Sounds as though you haven't split the application into a front-end database
> (containing the queries, forms, reports, macros and modules), linked to a
> back-end databases (containing the tables and relationships). Only the
> back-end should be on the server: each user should have his/her own copy of
> the front-end, ideally on his/her hard drive.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
> "sandrao" <(E-Mail Removed)> wrote in message
> news:5C4B7728-9119-4E0F-A933-(E-Mail Removed)...
> >I have a Database that was created in Access 2000. This Database is access
> > by several users theouth a network. What happens is that for some unknow
> > reason to me the Database will brop its name and be renamed db1. Then
> > what
> > happens is that the users cannot access it through its regular shortcut.
> > Example. The database name is "TravelInvoiceInvoicing" Then for some
> > reason
> > when the other users close the program it seems to drop the Name and it
> > becomes "db1". What causes this and how can we prevent it from happening?
>
>
>

It should. For one thing, each user's shortcut will point to the front-end
database on his/her hard drive, so even if User A had a problem, it wouldn't
impact any of the other users.

I suspect that the problem is caused by one (or more) of the users having
Access set to Compact On Close. That's seldom (if ever) a good idea.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"sandrao" <(E-Mail Removed)> wrote in message
news:22993112-E34D-4CDA-BFB0-(E-Mail Removed)...
> Would splitting the Database eliminate the problem?
>
> "Douglas J. Steele" wrote:
>
>> Sounds as though you haven't split the application into a front-end
>> database
>> (containing the queries, forms, reports, macros and modules), linked to a
>> back-end databases (containing the tables and relationships). Only the
>> back-end should be on the server: each user should have his/her own copy
>> of
>> the front-end, ideally on his/her hard drive.
>>
>> --
>> Doug Steele, Microsoft Access MVP
>> http://I.Am/DougSteele
>> (no e-mails, please!)
>>
>>
>> "sandrao" <(E-Mail Removed)> wrote in message
>> news:5C4B7728-9119-4E0F-A933-(E-Mail Removed)...
>> >I have a Database that was created in Access 2000. This Database is
>> >access
>> > by several users theouth a network. What happens is that for some
>> > unknow
>> > reason to me the Database will brop its name and be renamed db1. Then
>> > what
>> > happens is that the users cannot access it through its regular
>> > shortcut.
>> > Example. The database name is "TravelInvoiceInvoicing" Then for some
>> > reason
>> > when the other users close the program it seems to drop the Name and it
>> > becomes "db1". What causes this and how can we prevent it from
>> > happening?
>>
>>
>>

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com>

> I suspect that the problem is caused by one
> (or more) of the users having Access set to
> Compact On Close. That's seldom (if ever)
> a good idea.

And, I would add, normally useless if you have split the front- and
back-ends and given each user their own front-end.

Larry Linson
Microsoft Access MVP