Security Issues

[Quehay]

(Thanks Elizabeth for the FAQ link to MS security FAQ's but I still haven't found answers to the following<br>I work in a company with a large network--one that includes branch offices in several US and European cities.&nbsp;&nbsp;I want to be able to place the data tables of a split db on the network.&nbsp;&nbsp;Question:&nbsp;&nbsp;How can I best secure the data db's?<br>I am not the only Access developer and don't have the permission or even the knowledge to declare blanket user permissions per group membership--doesn't the .mdw file affect the global use of Access?&nbsp;&nbsp;<br>Question2: Also, where would I place the .mdw file if I were to use it? (The db's are kept in client folders rather than an Access-specific folder.)&nbsp;&nbsp;<br>Question3: With a split db is it practicable to have general password security on both ends?--I want to protect the objects from monkey business, but the data tables are ultimately even more critical.&nbsp;&nbsp;<br>Question4: Could an .mde front end be successfully linked (and re-linked) to data tables that had a general password security?&nbsp;&nbsp;This is a lot to field at one time--thanks for any wisdom shared!<br>Q

 

[ColinM]

Access basically isn't very good at security.<br>Might be better to move to SQL Server back-end if security is vital.<br>From memory I think you right in saying that the .mdw in for global Access use.<br>I wouldn't want to keep that file on the client as it can be overwritten (with the default) or deleted, not sure if you would be able to look at tables with a split db but you could change all the forms,reports etc.<br>