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.

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?