This message is related to the performance issue threads that were created a few days ago.

I made some robust test this morning on my 100000 records tables. Here's my result related to high volume tables.

1. Working with SET DELETE OFF is a must otherwise go get a cup of coffee

2. Even with SET DELETE OFF there is some gotchas I had to watch for.

2.1 Unlike 2.x, Visual FoxPro does not allow LOCATE and at least SCAN to be Rushmore fully optimizable anymore so applied those changes

2.1.1 I was using the LOCATE command to see if I was able to find at least one record in my table to enable the delete button. I now use the COUNT. I will also have to use the SEEK where I use LOCATE to retrace a specific record

2.1.2 SCAN was slowing down the test drastically. I was using a SCAN to replace a value in a few records. I now have to use a SQL and apply the SCAN on the SQL and use the SEEK to be able to apply my REPLACE

3. Now that I work with SET DELETE OFF, some changes had to be applied here and there

3.1 If I delete a record in a child table, I just put a negative value of my record so the relation will be lost resulting in the same effect as SET DELETE ON. Yes, I still apply DELETE on that record so it will remove on the pack or will be recycle on the next ADD

3.2 On my pick lists, I add to add the FOR UniqueId>0 so I won't get the deleted records