>>>Any idea why the tableupdate in the following code would fail. Note that this is a simplified version of my code. In my application I am actually updating five tables.
>>>
>>>SET MILTILOCKS ON
>>>SET EXCLUSIVE OFF
>>>SET DELETED ON
>>>
>>>USE mytable IN 0 shared
>>>=CURSORSETPROP("buffer", 5, "mytable")
>>>
>>>DELETE FROM mytable WHERE RECNO() <= 500
>>>
>>>BEGIN TRANSACTION
>>>IF !TABLEUPDATE(.T., .T., "mytable")
>>> ROLLBACK
>>> = TABLEREVERT(.T., "mytable")
>>>ELSE
>>> END TRANSACTION
>>>ENDIF
>>>
>>>The above test works when I only delete 499 records but when I try 500 it fails. Each record in mytable is 1426 bytes. I also have the same problem if referential integrity deletes the 500 records (cascading delete).
>>>
>
>Bill,
>
>A new clue! If mytable is located on our server (Novell 3.12) the tableupdate in the above code fails. If the table is located on my c: drive the tableupdate works. I tried the above example using vfp\samples\data\orditems and deleted 1500 records. It worked on my c: drive and not on the network.
>
>Any ideas,
>Shane

I believe that the network will also place it's own locks in addition to VFP's.
It sounds like some parameter in Novell that is limiting you to less than 500 locks.

Steve