Securing MDW files

[Mark Wild]

I am trying to find a way of securing my mdw,mdb and mde files in terms of preventing users from (perferably) seeing them and certainly being able to delete or rename them.

I have tried restricting the access via folder level security, but prevented the users from being able to access the system (ooops!).

I guess I am looking for a way to allow users complete access to the data within the folder (have security on the dbs) but prevent them from accessing the objects. Is this possible

Users access DB's from a shortcut held elsewhere

 

[ghudson]

Your network gurus should be able to set the access control for that folder to prevent file deletions and renaming.

Your users have nothing to gain by deleting or renaming the MDB or MDW files. Do you have that type of mischief in your company?

The front end and the MDW file should be on the users computer. You should have code in your secured db that will test for the back end file and close the front end if the back end file can not be found. That will also prevent somebody from using the db away from work or on another server (hard drive).

HTH

 

[Autoeng]

If you have properly secured you db's then the users cannot access them with out being an authorized user but I understand your concern about someone renaming the db or workgroup file. Because a user must be able to write to all of the files you list other than making the files hidden using Windows Explorer, (which if the user has "Display hidden files" turned on their pc, doesn't do you much good. Can a directory be made "Hidden"?

If you fear sabotage to that extent then I would back up the mdw file manually and code for back up of the database itself. If you search for "backup database" you should find some info.

 

[Mark Wild]

Thanks,

At the moment my network gurus are not guru'ing very well. It is for them that I am trying to find this out as they don't seem to be able to do it.

As for your comments about deleting mdw's etc, I completely agree with you. It should not happen! But...we're in the process of clearing down a large amount of files as the dept had 50gig of data and there have already been a few "mishaps".

I will look further into putting the FE and Mdw's onto each machine (I know there are a number of threads on this). I was told by IT not to do this, but if it will help and willing to do it.

Regarding mdw's on local drives, we often end up hotdesking. How can I be sure that a usre I added on one machine will exist on the next? At the moment its on the network, so not an issue.

Off for the weekend now, but thanks for the feedback so far.

Mark

 

[Autoeng]

I personally don't put the mdw down to the users pc but leave it on the server. I use a batch file to copy the FE to the users pc. If you want you can read a couple of threads I have posted to about batch file distribution by searching for user "Autoeng" and keyword "distribution".

 

[Mark Wild]

Thanks both of you. I guess I'm going have have to trust my users to behave...

I'll read up on the techniques of FE's and syncronising them when I get back in on Monday.

Cheers,

M