Thanks Ted,

I just realized that If I set deleted off, I get the correct results, so the first record with collector 31 must be deleted.    I will just use the SQL statement you suggested to make sure it's always correct.   Thank you.

From: Ted Roche tedroche@gmail.com To: "profox@leafe.com" profox@leafe.com Sent: Monday, November 28, 2016 3:46 PM Subject: Re: Index on collector tag collector unique

Pretty weird. That's a bug. Or perhaps a corruption in the existing indexes.

SELECT DISTINCT collector in MyTable ORDER BY collector INTO CURSOR YourCursor

can give you the same thing, real quick if you already have an index tag on collector, and even if you don't.

On Mon, Nov 28, 2016 at 3:30 PM, Michael Madigan mmadi10699@yahoo.com wrote:

Strange behavior I've never seen before I have a 3 character field called collector.    I have many records with collector= '31' .  When I index using the command "Index on collector tag collector unique"  I get every one except collector 31.  I get collector 3, I get collector 30, but I don't get collector 31.  There are over 2000 records with collector = '31'

I realize you have to reindex every time to make sure you have every collector accounted for, so it's not that

This is really odd.

--- StripMime Report -- processed MIME parts --- multipart/alternative   text/plain (text body -- kept)   text/html

---

[excessive quoting removed by server]