Question sharing database over several users issue

[marianne]

hi to all !

after I have shared the database over the network to be shared to users through shared folder, how do we protect now the database file itself from being deleted since the database file is seen from the shared folder. The act of deleting the database file maybe just mere error or deliberate by any person who can access the shared folder.

thanks.

 

[DCrake]

You need to be thinking about access rights of users who have access to the shared folder. Make sure that permissions do not include the ability to delete files.

Also make sure this shared network point is inculded in the normal backup routines.

Another trick is to make the actual mdb a hidden file so it cannot be seen by unsuspecting eyes, and if you can''t see it you can't delete it.

David

 

[marianne]

1. how will I do permission on the shared folder?
2. yes I can make the file hidden but I think it can still be seen when the folder options is changed. How will I do it?

 

[DCrake]

Speak to your System Administrator or IT dept to voice your concerns and ask for their advice.

David

 

[marianne]

I am not in a company, so I dont have any dept Sir. can you advice me instead!

 

[ByteMyzer]

For the Network Share that hosts the back-end file, set the End-Users' permissions to the Folder thus:
* Read & Execute
* Write

 

[marianne]

ByteMyzer, may i know what operating system that sets the folder permission like that because I am only using windows xp home and when I go to the folder properties, only hidden and read only attributes are there!

 

[oumahexi]

Marianne
Open the network drive and right click on the folder where your database is stored, select permissions and you'll see the options that ByteMyzer refers to under the security tab.

 

[SOS]

The users need to have

Read/Write/DELETE permissions on the folder (otherwise the ldb file will not close properly if the delete permission is not there).

Also, this should be a split database - frontend on user's machine and backend on the network share. If you don't split it and run it from the network share, prepare to have corruption issues.

See here for more about splitting:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[SOS]

And you make sure the network admin is backing up the folder that the database is in and if someone deletes it, then you have them do a restore from the backup.

 

[ByteMyzer]

marianne,

I recommend upgrading to Windows XP Pro.


SOS,

This is not true. The LDB file is System-generated, not User-generated. I have set up numerous database applications in a Windows Client network environment, giving the End-User group exactly the permissions as I described (NOT including Delete), and when all the End-Users have exited the application, the LDB file completely disappears.

 

[SOS]

and when all the End-Users have exited the application, the LDB file completely disappears.

Okay, if the file is opened by the user directly then they do need the delete permissions. If it is a backend file opened by a link from the frontend then perhaps they do not. However, I've experienced exactly the opposite of you in that we had an ldb file hanging around in the backend folder until we made sure the users all had delete permissions on the folder - so MS strikes again (inconsistencies).

 

[marianne]

I really appreciate the replies. but bytemyzer, what is the end-user only have home edition operating system and cannot avail of XP pro as of the moment, would there any other way to set permission to the folder or any other way to secure the db file so as not to be deleted by any user?

 

[ByteMyzer]

marianne,

I'm referring to setting up permissions on the Network Share on the host computer, not on the End-User's Client machine.