<I><FONT COLOR="#663300">Correct me if I'm wrong, the CB security system assumes dedicated computer for each person.
I think an intermediate measure is to allow someone to logout, but without leaving the application before leaving. The application is still loaded, but say, pads in the mainmenus and the toolbar are disabled (except the login button, of course).
Denis</FONT></I>
Greetings Denis,
Your idea is a good one. In the goapp.beforereadevents() place a method to determine if the application is using delayed logon mode. If it is...
push the menu and replace with a DelayedLogonMenu. That menu should have three pads: exit, help and logon.
You'll need to change setup.ProcessLogon() so that it returns .T. unless the DBA exclusive access is set. Then at some time after the real logon...
Set the UserID value. You need to modify the existing logon form because it uses a network global variable to determine who the user is. You won't be able to use SYS(0) or WinApi functions since the application has already been started by a technician. Look through the SaviSecurity classes. There is one ui that enables the userID field so that the user puts in both their ID and their password.
There is a method in goapp (and oSecurity) to .GetUserID() that you can use for timestamping, etc. But you need to set it after logon.
There is a cSession instance on the container holding the controls for SaviSecurityAdmin. Another one is added during init and this creates a known bug condition. I removed the instance in the design tool and left the dynamic addition in place. No problems. There was thread regarding this issue about 4 months ago. Search on cSession or session environment.
And finally... you'll want to think about a timer to close the application and return to waiting. Because user's don't always logoff.
HTH
James Sayer
©2001 James Sayer |
