Peter,
Yes, this is run from another .mdb. And it works, the same code with slightly different syntax was posted here about a year ago. But the 'database password' was never meant to be any more than cursory security to keep out the causal user. I'm more interested if this company has cracks for user-level security. Their website shows a screen shot with user-level security broken, but the 'demo' curiously doesn't demo that pariticular gem. Plus, they want $350 for the 'full' tool, which I guess is the one that cracks user level security.
The data that I (and I would hope anyone) secures with Access is never so critical that a breach would be devastating--else we wouldn't be using Access for that data. However, some of it in my case is data that I and the clients would very very much prefer the users not see, but the vast majority of my Access user-level security is to keep users from messing with the forms, reports, code, etc. If one of my users wants to mess with my forms so bad that they'll spend $350 to do so, then c'est la vie.
--Jim