Do you really need to go through a Cursor Adapter? Why not just write a tiny PRG that tries for exclusive use of the talle, then zaps it?
>Thank you. I will have to figure out a different approach. I will try PACK.
>
>UPDATE: Pack does not work either.
>
>>No. ZAP cannot be used against a buffered cursor/table.
>>
>>>Do you know (of course, I will test it today) if ZAP can be issued against a Cursor Adapter cursor? Because I am trying to avoid opening the table with USE command but rather do everything via CA cursor.
>>>
>>>>After DELETE you'll have table with 10,000 deleted records which can make even SEEK() slow. On other hand ZAP requires exclusive access to the table. I would go with later, if possible.
>>>>>
>>>>>I am opening and updating tables using Cursor Adapter. In one of the procedures I need to zap all records in a table. I can fill the CA cursor with all records, delete records, and then call tableupdate(). But my questions is, how practical this approach if the table can have up to (max) 10,000 records. This is a VFP database (not SQL Server).
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only