Hi Jim,

this behaviour ( BUG ) occur also on SPT command.

On various SQLEXEC(),
if complex ( correlate to SQL Server Query Analyzer time ? )
VFP report me this error ( .. Out of Resource ),
but this is not repeteable, then i don't open a Thread on UT
( This is a big limit of MS approach to bug:
a bug is accept only with repro code,
but for errors correlate to application timing can't exists a repro deterministic code;
ok you can use statistics on report bug or crash, but if this error it does not arrest the application, the bug cycle fix can delay more).

This bug isn't on REQUERY command but on VFP ODBC interface;

VFPT have rewrite VFP ODBC interface for support more complex
SPT script, for use more efficently ODBC statement handle on shared
connection.

I hope you debug with attention the VFP ODBC interface;
- VFP ODBC interface need to be very very ... very reliable,
any ODBC remote data (RV,CA,SPT) use this interface for enter/exit on VFP application.

Delay VFP8 SP1 publishing until VFPT are absolutely sure than VFP ODBC interface is timing correct.

Thanks!