|
Home > Archive > MS Access Multiuser > August 2005 > Folder permissions for a split database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Folder permissions for a split database
|
|
|
| MS Access 2K, Windows XP
====================
Hi,
I have a database split into FE and BE with User Level Security, and the FE
is converted into an MDE. Each user has a copy of MDE and I'm also using Tony
Toews's Auto_FE updater program.
I have follwoing folders on the shared drive:
1. BE (for Back end database file)
2. Master-FE (for master copy of FE file)
3. MDE (for MDE file that is copied to the C: drive if it is newer than the
copy on C: drive)
4. AutoFE_Updater (for StartMDB.exe and all INI files - I have more than one
INI file as different users have MSAccess.exe in different folders)
5. Wrkgrp (for the security MDW file)
The users also have a copy of the MDE on their desktops, and are accessing
the database using a short-cut that checks for the latest version of MDE, and
uses the MDW file.
I'm aware that the users need to have read-write permissions on the folder
that has the BE file. And, they probably need to have read-execute
permissions on AutoFE_Updater folder since the INI file is read, and they are
executing the exe file.
Do they need to have write access to the Wrkgrp folder and AutoFE_Updater
folder? What would be sufficient permissions for the MDE folder?
Thanks.
-Amit
| |
| Douglas J. Steele 2005-08-29, 8:26 pm |
| I don't believe they should require anything more than Read for the
AutoFE_Updater folder, but they'll need at least read-write for the Wrkgrp
folder. The permissions required for MDEs are no different than they are for
MDBs
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Amit" <Amit@discussions.microsoft.com> wrote in message
news:7CF7EEA6-D5F8-43BA-BF16- 1A4D541AAA9F@microso
ft.com...
> MS Access 2K, Windows XP
> ====================
> Hi,
>
> I have a database split into FE and BE with User Level Security, and the
> FE
> is converted into an MDE. Each user has a copy of MDE and I'm also using
> Tony
> Toews's Auto_FE updater program.
>
> I have follwoing folders on the shared drive:
> 1. BE (for Back end database file)
> 2. Master-FE (for master copy of FE file)
> 3. MDE (for MDE file that is copied to the C: drive if it is newer than
> the
> copy on C: drive)
> 4. AutoFE_Updater (for StartMDB.exe and all INI files - I have more than
> one
> INI file as different users have MSAccess.exe in different folders)
> 5. Wrkgrp (for the security MDW file)
>
> The users also have a copy of the MDE on their desktops, and are accessing
> the database using a short-cut that checks for the latest version of MDE,
> and
> uses the MDW file.
>
> I'm aware that the users need to have read-write permissions on the folder
> that has the BE file. And, they probably need to have read-execute
> permissions on AutoFE_Updater folder since the INI file is read, and they
> are
> executing the exe file.
>
> Do they need to have write access to the Wrkgrp folder and AutoFE_Updater
> folder? What would be sufficient permissions for the MDE folder?
>
> Thanks.
>
> -Amit
| |
| Paul Overway 2005-08-29, 8:26 pm |
| Just to clarify...they need Full Control of the folder(s) where the BE and
FE are located....otherwise, you'll have issues with compact/repair.
--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com
"Douglas J. Steele" < NOSPAM_djsteele@NOSP
AM_canada.com> wrote in message
news:%23NMEoROrFHA.716@TK2MSFTNGP10.phx.gbl...
>I don't believe they should require anything more than Read for the
>AutoFE_Updater folder, but they'll need at least read-write for the Wrkgrp
>folder. The permissions required for MDEs are no different than they are
>for MDBs
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "Amit" <Amit@discussions.microsoft.com> wrote in message
> news:7CF7EEA6-D5F8-43BA-BF16- 1A4D541AAA9F@microso
ft.com...
>
>
| |
|
|
|
|
|