>>All these ideas helped me move to a couple of other tests, and I have found that if the timer loop actually opens the database table, checks, and then closes the table ...voila! Now, a submitted request is responded to in the same second!!
>>
>>That seems odd, eh?! Does this provide any ideas as to what I might still be doing wrong? Opening and closing the table every 200 m/secs seems fairly bizarre and strenuous...
>
>Hmmm ... I assumed you were opening the table on the Server in a loop all along, and having problems.
>
>HOW WERE you trying to process the request before you put it inside the loop ?
>

.. simply by using go top (index is submitted ("datetime field - descending, filtered for Pending = .t.)

Based on your feedback and Jim's .. I will retry the set refresh command again ... I read the help file in the 2nd param .. but honestly was not clear on it's impact..

Scott