I think you need to provide more detail to get a good answer. I'm just now seeing this for the first time, as I rarely check-in at TT anymore.
That said, here are some thoughts:
[ol 1]
[li]Split database design. You did not specify your database design, but your tables should be in a separate database, always, whether that's Access, SQL Server, or something else.
This will provide additional security for protecting data tables besides better stability with Access applications.[/li]
[li]What is the password for? The database? Why does it need to change every 3 months? Is it a password for the entire database? Again, split database design would likely help here as well, as I would imagine you could assign 1 password to the backend and a separate to the frontend, and then the frontend could expire. Or maybe, again never tried, you could have a different password for each different front-end database. I'd want to at least consider that if I were handling this.[/li]
[li]Not sure of the details here, nor if possible because I've not needed to worry about it, but I would also want to see if Windows authentication could be used here to simplify it all. Then if someone should no longer have access, you remove (or have someone remove) that user's permissions to the database/folder.[/li]
[/ol]
"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57