Odd Occurence with Find

[Scott_of_MA]

I did something I've always done: Create a new field, specify as a Radial button (Yes/No), add it to a layout that is Viewed as a List.

I want to run a Find routine (show me all those entires marked "Yes"). I've done this numerous times.

For some reason, tonight, FMpro7 simply doesn't want to find it. It just says "No matters" found.

First that came up in Script, so I went to the Find manually. I see the row in Find mode. I click the "Yes" radial button option. I execute the find. Nothing.

Then I convert the Radial button to a regular Edit field. I show the list again. I see the same records now all have "Yes" written in them. I try and do a Find by typing "Yes" in that field in the Find mode. Nadda.

Finally, I delete the field, recreate from scratch, move it to the layouts, and try the above. Nothing.

Everything else is normal. I have a number of radial button fields in this database, some in the same layout as the main table, some relational. Every other field in that layout performs Finds as intended. I can't for the life of me figure out why this one time this one new field doesn't work. I'm going to ask some quick questions, and then will post a clone of the database if required.

Is there any chance that:

1) This field is corrupt?

2) There is a cap on the number of fields in a particular Table (there are 168 in this Table, and I have 8 tables, all relational in some way to this main one)?

3) The database has gotten corrupt somehow?

4) This has come up before for someone else and they have some insights?

Thanks!

[Ender]

If the field defined as Text? If not, this could account for your find problem.

[Scott_of_MA]

Thanks Ender.

It is a Text field. But based on your question, I decided to create a new Number field just to see if that would work. No dice.

The problem seems to be larger than this though. I don't seem to be able to create and search within any new Field.

Is there a maximum number of active Fields that can be created in a Table?

Does marking a field as Indexed do anything but increase the performance of search routines in a largish database?