AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Edit filemaker pro database9/6/2023 ![]() FYI, Ryan refers calls this functionality part of a larger idea called “Dynamic Views”: Ryan Klenk, of Anvil Dataworks, has posted what I consider to be the closet solution we’ll probably ever see to this problem. I have looked for an easy solution to this since the first time I used FileMaker (a long, long time ago). Click the save button to save, or the edit button to cancel and return to non-editable mode. Click the edit button and all fields were modifiable. By default, with no herculean programming by the developer, the data fields on a layout were not modifiable. Omnis 5 had a very simple set of buttons on the left of every layout: Edit, Save, and Cancel. But none of them worked as easy as one of the first databases I ever used (Omnis 5, if you must know. There have been plenty of tricks developed over the years to work around this issue: sessions, tabs, duplicate layouts with editable fields, and dashboards, to name a few. ![]() What FileMaker has always needed is View and Edit modes. We all have stories were the first record in the database is changed all of the time by unsuspecting new users. By default with FileMaker, the data is live and easy (some say too easy) for the end user to change. The user (and the developer, by extension) must make changes and submit them, causing an update command to run in order to make the changes. Most databases deliver the results of a query as a table, and the data is not usually directly modifiable. ![]() One of the most powerful FileMaker features is also a major weakness: the easy accessibility to edit records is both a curse and a blessing.
0 Comments
Read More
Leave a Reply. |