Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
From one COM object to another one
Message
From
25/03/2000 21:42:03
 
 
To
25/03/2000 20:20:46
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Miscellaneous
Thread ID:
00350435
Message ID:
00350463
Views:
19
>Michel,
>
>Dumb question here.... *g*
>
>Since you know that PhdBase only shows that ugly little screen once, why not do something like this:
>
>
>   if not thisform.HaveIEncounteredThatStupidPhdBaseBugYet
>      if thisform.CheckToSeeIfThatDialogIsOnTop
>         clear typeahead
>         keyboard {"Enter"}
>      endif
>   endif
>
>
>If your system goes down and then automatically starts then I'd just insert a call to a method/routine that forced a call to PhdBase, cleared the typeahead, manually entered something to clear the dialog and then proceed.
>
>I'd even bet that Ed Rauh, George Tasker or someone else could provide you a routine that let you know whether or not that pesky dialog was on top and could ..er.. eliminate it. *g*
>

I'd guess that the Wscript.Shell's SendKeys method could do it. I'd be worried about usability of PHDBase at all in an in-proc server because of this little issue. Maybe Rick Strahl has already seen it and has something in WebConnect to deal with this?
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
Next
Reply
Map
View

Click here to load this message in the networking platform