>Friday afternoon my manager brought to me a report that was leaving out one of our members. The report had 2 filters: one of them being a date field. I opened the table, browsed all members, and the member was there. I browsed using the 2 filters in the report, he wasn't there. Browsed using only one of the 2 filters, he's there. Browsed using the other (the date field), he's not. All of this is after proofing that the values in the fields being filtered are as expected. I even cut and pasted values from records that _did_ show up in the queries into the offending record to no avail. OK, I figure... something is messed up with the index, so after everybody went home, I reindexed. Voila! the member shows up. Well... s**t happens, so I went home. But today, there is another record in the same table that is doing the same thing. (but on different fields). What is going on? Could a funky piece of code cause an index to leave out records?
>PLease help... this random 'forgetting' of records just will not do. Thanks
>
>Erik

I can guess only. If you have report filters (like REPORT FORM ... FOR) and SET ORDER TO TAG ...., and this tag has filter expression itself, you actually add one more filter, i.e. depending what tag is active you can get different results. Could it be the case?