Restricting Access to Back & Front End

[pclutts]

My database has a front and back end. To get into the system, the user double-clicks on the icon for an Updater-Launcher that checks the master front end for new versions of forms, queries, reports, etc., before going into the database. The front and back ends are both on our LAN, but just in different directories. I know the best thing would be to put the back end on the hard drive of my PC, but due to constraints put on me by our LAN System Administrator, I had to put them both on the LAN. The system works quite well, but unfortunately a particular user or two insists on not using the Updater-Launcher icon. Instead, they bypass the Updater-Launcher and go directly to the front end to get into the database. This method of access prevents them from seeing any changes I have made to the forms, queries, reports, etc. Is there a way for me to force the users to access the system via the Updater-Launcher? Any advise is greatly appreciated. Thanks.

 

[KenReay]

Hi

How about capital punishment for the user?

Seriously..,

not sure about this, but perhaps you could extend your launcher to include a command line argument which can be read by the front end, if not present just give a message telling them to do it right and then quit the application (Application.quit)

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK