All:
I have a customer that is experiencing a very strange problem. There is a table that has a structural index (cdx) and one index key built with FOR !deleted() clause. The problem is when the table is natural order there are a number of records flagged as deleted however, when set to the one index order these same records are not flagged as deleted. My first thought was perhaps they used the table outside the application however, I'm pretty sure that is not the case.
Has anyone ever seen a problem like this or have any idea how this could happen?
Using FWH 13.02 and xHarbour Nov 2012.
