>Am doing passthrough SQL to Oracle 7.0 data store. The command "mexec = SQLEXEC(delete....)" takes 30 seconds or so during which the user has no indication the the machine is working. I decided to set the connection to asyncronous and I thought that it would allow a loop to run a poll the sqlexec command until it came back as something other then 0 at which point it would proceed. What I find is that with the connection property set to asynchronous, the sqlexec(delete...) returns +1 immediately. Am I missing the point of asynchronous setting?

Asynchronous is for retrieving large amounts of data. So the data keep coming even if FoxPro only shows the first 100+ records.

You could add a messagebox or change the mouse pointer to an hourglass to show the user that something is happening. I would check the where clause and make sure that the fields are indexed. That would speed the delete.