Lock back-end DB with VBA

[somm]

Hi,

I split the Db into back-end & Front-end. Problem comes here is the user is able to view tables and modify them from Back-end. So, i tried to lock back-end in exclusive mode but when i'm using front-end queries and forms it is giving error like "3031". Is there any way to lock/unlock back-end DB using VBA from front-end.



Thanks.

[RuralGuy]

I usually disable the AllowBypassKey and put a "Quit" form in the AutoExec Macro.

[ajetrumpet]

I usually disable the AllowBypassKey and put a "Quit" form in the AutoExec Macro.

so do I Allen. laugh. Is there any other way to do it though? Have you heard of another way by chance?

[ZMAN]

Where is the be stored (on a network?) On one computer with many users? What?

[pkstormy]

Ideally, I'll use SQL Server tables.

Another trick I use is to design a form that opens (maximized) on startup that 'looks' like the table listing. Once it's clicked on though, the mdb quits. I'll also put in some code so that when the backend is opened, it logs to a table with the user's loginID and date/time. This usually stumps a typical user and I'll notice the attempts (I also have it automatically send me an email with the user's name when the backend is opened.) A user typically tries to initially open the backend without the shift key and then uses the shift key if they can't get to the tables. If I then see the user's loginID and Date/Time they opened it (or an email), I go have a chat with them and discuss the importance of only using the frontend (telling them the exact date/time they tried to open the backend is usually enough to scare them from attempting it again.)

Typically what I do is have a MainMenu.mdb which has buttons to open any of the FrontEnd mdbs and I bury the backends in a folder the user wouldn't normally go to.

Another option is to implement MSAccess security on the backend.

Attached is an example of a fake background. It's main purpose is to capture who's trying to open the backend since no users should ever be attempting to open the backend. Once they open this mdb (typically without using the shift key the first time), you'll then know who that person is and the date/time (even though they may open it again using the shift key.)

[somm]

Thanks for suggestions. I'll try it in my DB.