

Fill the 'Subject' field with the correct background solid color instead of none, and enjoy your new precision search capability! The entire process is handled server side so it should not matter that client access is IWP.When the conditional formatting feature was announced by FileMaker some of us screamed “yeehaw”. Place that field over top of the 'idnumber' and send 'idnumber' to the back. To make it look correct you can insert another field, selecting 'Subject'.

The field will not look correct yet because it will show a number.

Now your drop down is the same clean selection as before. Select Also display values from second field: 'Subject' and Show values only from second field. This minimizes the effects of testing your changes etc.įinally, change your layout in inspector such that the drop down list shows Use values from field: 'idnumber'. I should mention that many recommend a best practice of never changing a production layout, but rather to duplicate the layout and make the required changes to the duplicate. Then from another layout assign each existing subject a unique idnumber, noting that if there are a great many subjects you could script that step. The trick here lies in making sure no two subjects have the same 'idnumber' even when you aren't paying attention, so set the next value to something greater than the number of subjects that already exist. The field type should be Number, and the options should include Auto-Enter-Serial number-Generate and On creation-increment by 1.

This solution requires you to add a unique serial number which is, in your case, to alter the Subjects table and add a field called 'idnumber' or similar. It is the use of that unique key that allows you to perform a precise search, even when the name of one subject is a partial or complete match for another. Rather instead you might want to search for a unique key whose subject name is 'Mathematics' as displayed in your drop down. You are searching for a name that is imprecise because it is a match for multiple names. This is a problem that is not necessarily unique to FileMaker.
