Ok, I sit corrected on that - I thought one timeout was pretty much like another. But still no love with the Sleep in the WinAPI. Also, no love with the DoEvents Force



>Hi Dorris,
>
>wait timeout is not the same as the win32api call. The idea is to allow windows events to process. This can be done as Tore mentioned, or with DOEVENTS FORCE, or with inkey(.x) where is is 10ths of a second.
>
>Now, does that control have a event interface? If so, then there might be an event for which you are supposed to be waiting. Directions for hooking activex event interfaces are available in the helpfile: it's drag-n-drop from the object browser, and a couple of lines of code.
>
>Hank
>
>>>>Ok....same ActiveX control
>>>>
>>>>if I run the code with a 'suspend' and step through, it gives me the correct information (Scanner exists, server exists). If I take the suspend out and run the code, it tells me that the Scanner doesn't exist, nor does the server...
>>>>
>>>>What the Huh?
>>>
>>>Maybe some control needs some extra time? Try to add some delay after one of the lines

>>>Line 1
>>>DECLARE Sleep IN WIN32API Long
>>>Sleep(1000) && One second
>>>Line 2

>>
>>Tried using WAIT TIMEOUT 5 (wait 5 seconds), didn't help. put a Wait Window in the OnScannerStatus method and it's not showing up. I'm really beginning to hate this control, and any questions like this that we send to M2Sys, we get the response that "They don't know anything about FoxPro" and that's it.
>>
>>It's almost like the event is not firing off without the suspend