>First of all, if you need to ZAP regularly, you really should rethink your design!!! Zap is something you should do max once or twice per year, inside a custom maintenance routine.
>
>Maybe you can use cursors for some of your work? Also read Set Deleted in Help.


Uhhh, nope
If you design a high-throughput system with many local physical discs, reading from several and writing always to an uninvolved/minimally involved physical disc throughput is MUCH higher compared to a system using several cursors for source AND target as you cannot define several physical cursor directories each living on a separate device. SSD much better, but still having separate source and target physical devices is faster - but not as much as on traditional HD. Zapping is faster than closing, deleting and creating ;-))

I am still waiting if MS will implement that as a CR - it was deemed an interesting idea but was not included in vfp9 update...

>
>For an answer to your question: In order to be "allowed" to zap a table, you must first Use the table Exclusive.