The active field, active tab or slide control and/or active portal row will be lost, causing the user frustration. Now, I could have simply switched layouts without the new window but a lot of contextual problems will occur.
The example file also includes a simple CONTACTS table to serve as the table being tracked. In the included example file, this table is called LOG. The result of the $Field variable might look like the following (the invisible carriage return is shown):Ī new window is created next, including a context change to a layout based on the table where the changes are being logged. A return separates the two values, making it very easy to parse, as you'll see later. The second grabs the active field name and concatenates it with the current contents of the field. The first is the primary key uniquely identifying the current record. It may even make your script run slightly faster cause the window is not being frozen and then redrawn. FileMaker has gotten a lot better over the years at reducing temporary window redraw so take advantage of it and make your script shorter. What I'm trying to say is, if you don't need the Freeze Window script step, then don't use it. I'm using FileMaker 19.2 on a Macintosh running Mojave and didn't notice the difference when freezing or not. Screen flashing could also occur on Windows, given how Microsoft redraws the screen as compared to the Macintosh. In older versions of FileMaker, the opening and closing of a new window could cause undesirable redraw screen flashes. The first step freezes the window because a new window is opened, manipulated and then closed. Let's start by covering the approach, identifying the issues and then solve the stated issues. It's not that the wrong way doesn't work or fails in a multi-user scenario, it just has shortcomings. This will facilitate reports and searching and even roll backs, if desired. The log will be entered into a table with each field being a record. The idea with this solution is to use script triggers to track any changes to specified fields.
It's not necessary to read the first article but I thought I'd let you know about it in case you are trying to come up with the best solution to log changes.
#Indirection in frozen how to#
This article is a second in a series of articles on how to track field level changes.
We'll start off with the wrong way to script an event log so you can get some perspective but will end up with a dynamic solution that can be copied and pasted from FileMaker file to FileMaker file. But, do you know the right way to script a field modification log? I've been programming them for years and have gone through every version of them and have settled on what I'm going to cover today. Scripting a change log table has been around since script triggers were introduced in FileMaker 10. Today, modern FileMaker files are stored in Unicode so I'm not sure if the phrase is still there. No, it's not a virus! My understanding is the developers just needed to take up some space in the header and that's what they came up with. What a lot of developers do is create a table called "Globals" to house all their global fields and unclutter other Manage Database tables.ĭull Boy FileMaker files were stored in clear text prior to FileMaker 7 so, if you opened a FileMaker file in a text editor, you could see the phrase "All work and no play makes Jack a dull boy" in the header repeated over and over. The same is true between two files in the same solution as long as there is a reference setup between the two files (External Data Source). No Relationship Needed Global fields can display in any table within the same file without using a relationship. Email John Mark Osborne or call John Mark at (909) 393-4664 to find out more about this service. Over programming hurdles via GoToMeeting. Meta-consulting is a service Database Pros offers to help other developers The Philosophy of FileMaker recommends PCI! Support this site by clicking on a sponsor below or becoming a patron! The Philosophy of FileMaker - Scripted Change Log
0 kommentar(er)
