>>That would be a good solution if we could allow program execution to continue but we can't. Usually the next form to display depends on the contents of the cursor being built so we have to wait. Any other ideas? Thanks for your help!
>
>As I understood you don't want the "Executing Remote... Press ESC to cancel." message from appearing, so the setting I talked about will take care of this issue.
>
>what do you mean by "Usually the next form to display depends on the contents of the cursor being built so we have to wait", please explain.
We are developing a system that displays information that is kept by geographical area and time period. The user first has to select the geographic area. This is done by clicking the appropriate button on a form which then runs a query to determine the time periods available for that geography. This query has to be complete before the time period selection form can be displayed.
The help file for SQLEXEC says that to run a query in asynch mode you have to keep executing SQLEXEC until it returns something other than 0. Here's the code I used to test this:
*********************************************
lnResult = 0
DO WHILE lnResult = 0
lnResult = SQLEXEC(myhandle,"SELECT * FROM Siccode")
ENDDO
RETURN
*********************************************
When this code runs, the "Executing Remote... Press ESC to cancel." message flashes on and off while the query runs!
I guess I'm missing something here. Any ideas? Thanx!
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
