1 of 1 people found this helpful
This is a bug in the handling of extracts and has been discussed elsewhere - it happens often when a Tab 7.0 file accesses Tab 6 extracts. I don't know if there is an easy fix.. After backing up what you have somewhere, try rebuilding the extract. If not, you may have to go back to an existing backup.
Thanks Alex. I will try
You may also want to try support@tab to see if they have any suggestions.