James,
What is the Asynchronous setting for the remote connection. By default, the setting is .F. and this means that SQLExec statements run synchronously. It waits until it is completed to return control back to VFP and move to the next line of code. If the setting is Asynchronous and the SQLExec statement takes a relatively long time, your program could move on in the execution cycle before SQLExec returns a response.

BTW, I would upgrade to SP3 to fix other problems with VFP but I don't believe that has anything to do with this problem.

HTH.

>Guys,
>
>I am currently using VFP 6.0 Service pack 2.0 and SQL Server 7.0 Service pack 1.0 on an NT server with 28gbytes of disk and 256mbytes of RAM, running NT 4.0 Service Pack 6a.
>
>I am finding that on an intermittant basis some of the SQLEXEC calls to SQL Server are being 'skipped' instead of being run. If I suspend after this happens, and force the SQLEXEC line to re-run then it works fine. - This seems like a similar error to the VFP 3.0 problem with VCX's and the introduction of _VFP.autoyield in VFP 5.0.
>
>Does anyone have any ideas as to why SQLEXEC command may not be running. An example of one such statemen is:
>
>LPARAMETERS lcInvID
>
>=SQLEXEC(this.loHTML.lnconnection,"EXECUTE family_get_parents '"+lcInvID+"'","_tmpParents")
>
>Return .T.
>
>
>Do I need to install Service Pack 3.0 for VFP?
>
>Many Regards,
>
>James.