I have an Access 2002 database that has recently been
mounted in a shared folder on Small Business Server 2003.
It is set to auto-compact when the file is closed
(basically to stop the users having (ie failing) to
compact it periodically).
The problem is that when a user closes Access, the
compaction process automatically creates a copy of the
database and gives it the original name. In doing so, the
access permission are set so that it becomes a 'personal'
file of that specific user, and no-one else can open it.
Is there any way around this? If someone has to login as
Administrator and compact the file periodically it just
isn't going to happen!
Thanks
Ian
david epsom dot com dot au - 26 Jul 2004 01:16 GMT
Compact always creates a new file and deletes the old file.
There is nothing you can do about that - that's just what
it means when you compact a file.
The new file will always get the permissions assigned to
new files in that folder, and the owner will be whoever
is set to get ownership of the new file (that is some
kind of windows setting).
Also, compact of a network file means that the whole
file is slowly brought across the network, recreated
in memory on the workstation, then written slowly back
across the network.
When you have a network file, it is probably better to
just compact the file every year or so, rather than doing
compact on close.
(david)
> I have an Access 2002 database that has recently been
> mounted in a shared folder on Small Business Server 2003.
[quoted text clipped - 14 lines]
> Thanks
> Ian
Frank Konzal - 26 Jul 2004 14:49 GMT
Are your permissions set to the file level or folder level? It sounds
like the permissions are given to the file which is not being used once
it is rewritten to the 'new' file with the same name.
> I have an Access 2002 database that has recently been
> mounted in a shared folder on Small Business Server 2003.
[quoted text clipped - 14 lines]
> Thanks
> Ian