On 2013 Sep 18, at 11:35, Nick Adams <[email protected]> wrote: Hi, Call me a fuddy-duddy, but I've never learned to trust those $$ script variables to still be there when I really need them. I always create actual fields for the storage of information that I want to preserve from one moment to the next. I keep them in a table called siimply "F" (for "file"), which contains exactly 1 record and is cartesian-product ("x") joined to every record in every other table, so absolutely the entire database knows the value of every field within "F". I also have 2 standard scripts that I include in every file, "Remember Location" (which is invariably called from within other scripts, typically "Go to" scripts) and "Refind Current Record" (which is sometimes called from within other scripts but sometimes button-activated all by itself). I expect that you can draw upon their principles to generate script-triggered equivalents. Here are the particulars of each: |
So every place in the entire file knows what "F::Layout Saver" is. And here's how they get back there (and, more particularly, how they get back to the exact record within that layout): |
Each of those "XXX Saved" table occurrences is based on a link from "F::Seq Saver" to the unique sequence number of the desired table. |
