>Ed,
>
>Dunno, but unless & until Jim K. provides a fix anyone that uses the product is going to have to find something that will wouk in unattended mode.
>
>Now, not to argue with you that WSH is the end-all to be-all *g* but if either it or VFP can make it happen that's what counts for me at the end of the day.
>

Doug, my worry about PHDBase here wrt an in-proc server is the issue of what context the messagebox is being raised in - you need to direct a Windows message to get the messagebox to "Leggo my Eggo!", and let's suppose that I made use of PHDBase in a VFP in-proc server, perhaps under MTS, where there's no way to pre-fire the messagebox, and under MTS, nothing to sit and send the message indicating to PHDBase to sit down and shut up, especially if it's actually running on another distant system, which wouldn't be aware that PHDBase was sitting and waiting. This may preclude using PHDBase for VFP COM applications; it's not something I've explored. If PHDBase is something needed for a mid-tier component, especially one where deployment via MTS or another pool manager is an issue, and where there are I/O events that require an unusual intervention through a perhaps non-existant direct UI, this might make it imperative to either get PHDBase to fix the offending behavior or find an alternative tool that doesn't exhibit the objectionable and troublesome behavior.

>Best,
>
>DD
>
>>>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?