This makes sure all indexes (including the Record Index) are being rebuilt and are up-to-date. If you can't delete a Record with all fields containing question marks - and you usually can't - make a Clone of the original file and Import the data from the original file, table by table. This problem almost never appears though. The original data is rescued although it now has a new Record ID. If a Record (that would otherwise be lost) can be shown through a Find or Go to Related Record, Export it to a new table or file, delete it in the original table, and then re-Import it (auto-enter option off!). This index is rebuilt with every new Find and hence never an issue. This makes sure all indexes are being rebuilt and are up-to-date. Make a Clone of the original file and Import the data from the original file, table by table. Please note: simply updating FileMaker Pro does not cure any pre-existing index flaws. How do I know there is an index problem with my file? Depending on the Index Type there are different symptoms indicating a flaw.Īfter Show all Records, a Record entered earlier is not shown or all fields appear as a question-mark.Ī Portal or a Go to Related Record either shows more than or less than the expected number of matching records, or all Fields of one Record appear as question-marks.Īfter a Find either more than or less than the expected number of records containing the searched Word are shown, or all Fields of one Record appear as question-marks.ĭepending on the Index Type there are different methods to salvage the index - if at all possible.īefore any further action, make sure to use FileMaker Pro 9.0v3 or later, which fixes a bug that might make FileMaker Pro under specific conditions "forget" to reset an index bit and hence such non-existent Records show up with question-marks in all fields. So what problems can arise, how are they recognized, and possibly cured?Īs we have seen, a single bit can make a big difference for the functionality of a file. There are many kinds of indexes: Index Typeīits representing the Record IDs in a Base Table of So for example, in a Base Table, every new Record sets exactly one bit at the position corresponding to its ID. This index is used to Find all records in a table that (for example) contain specific words (or parts thereof) within a field.Īn index is stored as one bit per corresponding Record ID. Using numeric indexes (containing no spaces or other characters) is therefor very space efficient. Numeric fields - these include date, time, time stamp, and number fields - use up to 400 digits for the value index. The remaining characters and words are ignored. In a text field, the first 100 characters of each text line - regardless of being spaces or "real" characters - are taken as the key entry. This index is needed only for Relationships. So what exactly is a Value and a Word Index? The meaningless "Minimal" would be better substituted by "Value Index" and "All" by "Value and Word Index". For number, date, time, and timestamp fields, as well as calculation fields returning results of these types, All creates an index of a field's values. Prevent FileMaker Pro from indexing the field.Ĭreate a value index of a text field’s contents or a calculation field returning text results.Ĭreates both word and value indexes for text fields or calculation fields returning text results. While None seems clear (no index exists) this does not mean, you can't search in this Field - it just takes significantly longer, since the search field of every record has to be compared to the search criteria.īy contrast the options "Minimal" and "All" are not clearly explained in the FileMaker Help (quote): In the Options for a Field the user can choose between an Indexing of None, Minimal, and All. "Ooh! My Record shows just question-marks in all fields, what's that?" What you should know about FileMaker Pro Indexes The FileMaker® Pro Indexes and Related Problems
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |