Hi Mel,

>I haven't been able to completely... it just makes no sense. If you run Dave's sample apps, they don't do it.
>
Same for me. The sample app works fine - but it uses a different login form I noticed.

>And, I have some user's that just sit there and wait. It has been an issue.
>
I finally got it to stop the hourglass after login, but ended up without a mouse pointer until the mouse is moved or a key is pressed.
Here is what I did to my appmain:appapplication.beforereadevents

local llRetVal as logical

* Require successful logon before application may continue.
* If you dont care about secutity issues, you can remove this line.
llRetVal =  IIF(ISNULL(THIS.oSecurity), .T., THIS.oSecurity.AutoLogonDialog())
keyboard '{dnarrow}'
_SCREEN.MousePointer = 14 
*RaiseEvent(_SCREEN, 'MouseMove',0,0,Mcol(),Mrow()+1)

return llRetVal

The commented raiseevent() I thought would get the mouse pointer back, but It didn't. However, I real move of the mouse will.

>Dave (at CodeMine) did tell me he would look into and fix it, but it wasn't at the top of the list.
>
Good to hear.

Thanks the info Mel,
Cris