![]()
And really, these are the types of errors that can go hidden for a very long time, possibly forever. Filemaker pro serial number update#If the table is locked and there is no error handling for such a case, however, the script could update the wrong record and the user would never know about it. It is a very common practice, immediately following a New Record / Request script step, to use a Set Field step (or multiple Set Field steps) to set values into various fields in the new record. Even though records cannot be created until the lock is released, existing records can still be updated. This is really important, and is where data integrity issues can be introduced. ![]() This will occur if, say, a user clicks the New Record button in the Status Area, but what would happen if the record creation occurs during a scripted process? And to further complicate things, what if a developer has added a Set Error Capture script step? Depending on where the Set Error Capture step is added, FileMaker might not display a dialog. If a user tries to create a new record, manually, while a database developer is doing one of the above activities, FileMaker will display a dialog alerting the user that an error was encountered. This is really important when a table is locked, no new records can be created in the locked table by a user or a script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |