Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
OApp.Logout() in VMP
Message
General information
Forum:
Visual FoxPro
Category:
Third party products
Miscellaneous
Thread ID:
00366835
Message ID:
00366907
Views:
12
>When I issue an oApp.Logout() my application kind of jumps around on the screen a little as the menu and toolbars etc are released. Is there a way to avoid this?
>

It's a SWAG, but if your forms run in the context of the main VFP Window, try:

_SCREEN.lockscreen = .t.

If the Forms run as top level forms, try issuing:

thisform.lockscreen = .t.
DODEFAULT()

in the Form's Destroy event. If they run in the context of a parent top level form, set the top level forms LockScreen = .t. before releasing the child forms, and use the previous code in each child Form's Destroy().

You could also create a Modal ShutDown Form that brings itself to the top, sets all members of the _SCREEN.Forms collection .visible = .F. so that it can't be seen during shutdown. And dozens of other ways...

>I originally had bypassed the oApp.logout and used some original code that just released oUser and presented another user login. However, now that I am using the security I do need the menu to be recreated specific to the new user lanid.
>
>Maybe another solution would be ... Is there a way to refresh the menu after a user login. That way I wouldn't have to release everything I could use my original code and then refresh the menu when the new user logins in.
>
>Thanks,
>Paul
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform