[AccessD] Password protect 2007 db

[James Button]

I'd add not to forget to ensure the .db__ files are actually secure from access
- deletion, replacement, or reversion via direct access or directions to the
facilities backup/restore facility by any NOT-authorised persons.
For general auditing I would expect the facility to record 'who' accessed the
facility, when, and what they did - those 'who's being checked (password etc.)
by the OS, and then against a list of authorised users.  

Problems I experienced with a DB facility on a client's systems.
Also worth ensuring that the back-end includes something that will function as a
version check for each 'facility' linking to it - maybe a pair of timestamps -
last structure/code change  and  last 'application' backup taken. 

JimB

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark
Simms
Sent: Friday, January 29, 2016 7:15 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Password protect 2007 db

I discovered it's impossible to open a password protected back-end from a
front-end programmatically.....
Unless the code to open it resides in the backend. In that case, you must
password protect the VBE.

> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of FW Salato Center
> Sent: Friday, January 29, 2016 1:58 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Password protect 2007 db
>
> https://support.office.com/en-ie/article/Encrypt-a-database-by-using-a-
> database-password-fe1cc5fe-f9a5-4784-b090-fdb2673457ab#bm2
>
> I need to password protect an Access 2007 split database, which will
> have a handful of people accessing it regularly. I don't need serious
> protection as I'm not worried about someone stealing info. It'll be on
> a server with company access and I just need to stop agency-wide
> employees from accidentally opening it and doing damage. I'll have
> regular backups and nothing's confidential. I'm just trying to avoid
> unintentional access.
>
> This seems good enough to me.
>
> Thoughts?
>
> Susan H.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com