Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Put an MDB backend in a hidden folder on server
- Thread starter Hfnet
- Start date
Back it up for sure, but what are you protecting it from?
If protecting records and objects, then apply Access security implementing user/group security.
If protecting the file itself, then have your network admin help you setup a network directory with permissions of read/write, but not delete/rename/move/and...etc. Delete permissions are nice so Access can delete the .ldb file and you can see when it is open, but I believe Access will still run fine if it doesn't have permissions to delete the .ldb file. But you might want to double check on that.
With this, it shouldn't need to be hidden.
Or am I misunderstanding what you want to do?
Mike Dorthick
If protecting records and objects, then apply Access security implementing user/group security.
If protecting the file itself, then have your network admin help you setup a network directory with permissions of read/write, but not delete/rename/move/and...etc. Delete permissions are nice so Access can delete the .ldb file and you can see when it is open, but I believe Access will still run fine if it doesn't have permissions to delete the .ldb file. But you might want to double check on that.
With this, it shouldn't need to be hidden.
Or am I misunderstanding what you want to do?
Mike Dorthick
- Thread starter
- #3
I am facing a similar problem. I don't use an mde but let end-users run queries in a vbscript client-sde interface (only IE is used in the company).
The problem is that they only have a read access on the folder where the db are stored, and they can't access the data as the ldb cannot be written. All I found on the web since I am working on this is that users need a write AND delete access to the folder, which is not an option for me...
If I create an mde, and I guess, creating queries that won't be accessible to users, will I be able to acces a back-end database with some kind of functional userID having a full change access ? What will be the impact on performance in that case ?
If you have any general advices that would help me a lot...
E.
The problem is that they only have a read access on the folder where the db are stored, and they can't access the data as the ldb cannot be written. All I found on the web since I am working on this is that users need a write AND delete access to the folder, which is not an option for me...
If I create an mde, and I guess, creating queries that won't be accessible to users, will I be able to acces a back-end database with some kind of functional userID having a full change access ? What will be the impact on performance in that case ?
If you have any general advices that would help me a lot...
E.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question