Doug Steele
dbdoug at gmail.com
Tue Dec 22 08:47:12 CST 2009
The only time I've had a need for real data security - a payroll database - we decided that the easiest method was to use the existing network security. It was truly secure and easily modifiable as needed by the network administrator on site. So I just made two BE databases for the FE; the confidential BE was on a drive only accessible by payroll personnel, the 'open' BE on a publicly accessible disk share. The FE to confidential BE linking code would just exit gracefully if it failed. We password protected the open BE as well, just to keep out the curious, but a couple of weeks after implementing this I had a conversation with one of the (electrical) engineers there. He told me the password and asked why we'd bothered! Doug On Tue, Dec 22, 2009 at 6:19 AM, Susan Harkins <ssharkins at gmail.com> wrote: > A reader has asked about Access workgroups security and I told him the > truth -- won't keep out the determined, but a good security setup > nonetheless. Now he wants to know what is. I should've heard that coming... > > I'd like to hear thoughts on Access security and alternatives -- strictly > opinion and war stories, you don't have to tell me how to use it! ;) > > Susan H. > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >