The found column is a bit of an enigma, and needed attention, but first some history:
Before you could add/remove columns to the display view there was a special case made for the found status. Tools=>Options=>General will allow you to set the "manual update of cache found status". When this option is checked the found column becomes visible and you can update it. Not only this, by checking this box you alter the logic of how GSAK updates the found status when you load a GPX file. That is, when this box is checked the found status will only be updated if the incoming GPX has this cache flagged as found and the database shows it as not found. The logic behind this being that if you are manually updating your finds, you don't want the next GPX file changing them to not found.
With the addition of the ability to add and remove columns, this is now inconsistent and needed changing:
1. Remove the "manual update of cache found status" option
2. Add found to the list of columns that you can add/remove from the display
3. Allow the user to decide at time of loading the GPX file how founds should be updated.
Item 3 has now been included in the Load GPX dialog and has 3 options:
Always - the found status of a cache in the database is always updated to whatever is in the GPX file you are about to load. This would be the shipped default.
Found only - The found status is only changed if the incoming GPX file has the cache as found, and the database has the cache marked as not found
Never - The cache found status is never updated by the incoming GPX file