May 6, 200421 yr Is there any way to trigger a script (or 'push' a button) via a field entry and then tab to next field. I know this hasn't been possible in the past - wondering if any advancements in V7. thanks
May 7, 200421 yr FM Developer 7 includes a "sample" plug-in that is meant to allow activation of scripts. I haven't had time to play with it yet, but it's on my list of things to do.
May 13, 200421 yr There is an example file at databasepros illustrating the use of this sample plugin. Pretty cool....
May 13, 200421 yr I'm so used to the old way of pushing a button to run a script, I'm not sure where this will be useful. Field validation is one possibility. Any other ideas?
May 14, 200421 yr All right, I've come up with one cool use of triggering a script from field entry (although it's sort of a field validation): I don't like to use regular field validations because they can pop-up in unexpected places. Instead what I like to use is calculated flags that mark data entry sections complete when required data has been entered correctly. But these calculations can be slow to redraw over the WAN (some are unstored). I'm using calculations instead of scripts because I want the flags to immediately indicate when fields are complete, without the user having to hit a Process button. Triggering a script after entering field data could be the best of both worlds: calculations when data changes, but stored results in regular text fields. A flag setting script could be triggered every time one of the data entry fields is modified. I'll have to test performance of this, but it seems promising. Any other ideas on where this feature can be used to "amaze your friends"?
May 14, 200421 yr There are three main events that I can see that will trigger a script using this plugin function. 1. With an auto-enter calc, it will trigger whenever a field is modified 2. With validation by calc, it will trigger when a record is committed (this changed from v6 to v7?) 3. Creating a calc field containing this function, triggers a script when a record is created. Combining these events with the use of OSX crontab and applescript (or ActiveX on windows if you're into that sort of thing) The need for events plugins is diminished. Are there other triggers that anyone can envision using this plugin for?
Create an account or sign in to comment