Just a WAG but use CURSORGETPROP to see what the setting are for FetchSize and MaxRecords on the machine and for the VFP version where it is failing. Then compare that to where it is successful. Normally they would be set to -1. Use CURSORSETPROP(propertyname, -1, 0) to set each property to what it needs to be. By passing 0 for the workarea as the 3rd parameter, these settings will be used for any cursor created AFTER the property is set.

>Using an Oracle 9 database but with an Oracle 7.3 odbc driver (SQO32_73.DLL - 30/06/19999).
>
>The Client's current system is being moved from VP6 to VFP8 (approaching deadline)
>
>In the version 6 application the following command works:
>
>

Machine A - SELECT * FROM <Schema>.<table> WHERE <filter> FOR UPDATE NOWAIT

>
>The query is sent via the SQLEXEC function and it returns 1 (all good) when the command is used on both VFP 6 and VFP 8.
>
>On Machine B, the same code as for Machine A is sent to the server.
>
>Using VFP 6, an error is generated -

"ORA-00054: resource busy and acquire with NOWAIT specified"

after running SQLEXEC().
>
>However, using VFP 8, no error is generated and updates are allowed on the "locked" rows.
>
>I've tried using SQL Navigator and different machines and the lock failing is repeatable.
>
>Can anyone help (or understand me).
>
>Thanks
>
>Clint