Find results are giving an unmatched value?

[whoo-whoo]

Hello, I have a Line Transaction table with about 113,000 records in it. When I enter Find mode, and enter 14022 (for example) in the "Contact ID" field, the results show 83 records found, 82 of which have 14022 in the Customer ID field and ONE which has 14029 in the Customer ID field.

I've included the screenshot below to help explain myself... note the circled value near the bottom!

Thanks for any ideas or things to look out for...... never had this happen before.

[LaRetta]

Click into that circled field. I suspect there are two entries separated by carriage return. The find would include this record because each line in a field is treated separately when searching. If that isn't it then I would suspect indexing issue.

[Christine Sephton]

Please also be sure that your field is defined as a number field.

[whoo-whoo]

Thanks for your replies!

I checked for a carriage return and there is nothing in the field except for the numbers 14029. And yes, it is a number field.

Where would you recommend starting with an indexing problem? (Not very familiar with that kind of issue.)

[LaRetta]

Go to ContactID's field definition, select Options > Storage. Set indexing to 'none' and uncheck auto indexing. Exit out of field definitions then go set it back like it was. Has the file ever crashed (particularly while being served)?

UPDATE: You can also use advanced Recover options if you want to reindex all fields at once. Set 'copy file blocks as is' and only check 'rebuild field indexes now'. This will reindex all fields but leave the file intact. Normally a Recover should only be used after crash to retrieve data for import into new clone.

[whoo-whoo]

:yourock:

Thanks LaRetta! I re-indexed the Contact ID field and it returned an accurate list. What a great feeling.

I'm not in the office regularly but a crash is certainly not unheard of with our setup, so I guess this is the evidence. FMPA 10 runs on an XP workstation and then another workstation on the same network opens it remotely. I'm sure one of the machines has crashed in the last little while.