Steve,
The trick is to _not_ impose a wait state on the server, but instead on the browser. You need to use the meta-refresh HTTP header to have the user's web page periodically refreshed (every 3 secs or so), and on each trip back to server, your web app needs to poll the messaging DBF to see if back-end processing is complete.

Each time a refresh occurs, you increment a counter that you include within the query string of the URL in the meta-refresh tag (which is easy since you are dynamicaly generating this). This lets you decide when to determine if a failure has occurred, e.g., after 5 tries or something.

I use this technique and it works well.


>I have a need to induce a wait state in a stored procedure I am calling from ASP via vfpoledb.
>
>I have tried several approaches, none of which is successful.
>
>Here is what I have treid so far:
>
>

>Wait "" Timeout 1
>

>
>This results in a "feature not supported" error message.
>
>
>I have also tried:
>
>

>
>Declare Sleep In Win32API Integer nMilliseconds
>
>nSleepSeconds = 1
>nMilliseconds = nSleepSeconds * 1000
>=Sleep(nMilliSeconds)
>
>

>
>This also results in a "feature not supported" error message.
>
>I have also tried:
>
>

>Do While .... some expression ...
>   For i = 1 to 10000
>   Next i
>   ... do something ....
>   Exit
>EndDo
>

>
>This results in the web server being tied up and slows down all processing. Not good!
>
>I can't believe this is that difficult. I keep feeling I am missing something obvious.
>
>Any ideas?
>
>Thanks,
>
>-Steve Kanski