Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Crash with EventScript

Featured Replies

Hi all, I have a really annoying problem - I have a database, where i created simple logging system - every logged field runs an eventscript (by validation -

Let ($x = S4HU_EventScript( "Incidents" ; "Log Field(ID, fName, fValue)";ID & ¶ & "Type" & ¶ & Self); 1)

Then, I have a second database, where i have that Incidents database listed trhough portal. And when i change any logged field in that portal and without commit run another script/jump to another database or anything else, the whole filemaker crashes. It happens just sometimes and it never happens when debugging.

Through Custom messages i found out that it crashes on first script step - setting variable $params=Get(ScriptParameter) .. I tried to put Commit, Flush cache and these last-hope steps to avoid that, but i never succeeded. Did anyone get the same or similar problem? Or hopefully - had anyone solved that problem? I would be really greatful for every help..

P.S. I tried to download new version fo eventscript, but nothing changed..

Your problem shouldn't fall under this by any chance:

http://www.softs4humans.com/support/eventscript_known_issues.htm

However - Is it urgent to create new records, when logging?

--sd

  • Author

Well, my logging system doesnt create any new records at all.. He just works with only Log field .

Example:

19.3.2009 13:53:25: Iveta set Type to Event

19.3.2009 13:52:21: Iveta changed Supervisor from Iveta to Ivan

19.3.2009 13:50:20: Iveta changed State from Active to Completed

My log is based on custom function, to which i send content of that Log field, new field to be logged and new value for that field. By using many functions, like Left(...), PatternCount(..) etc it finds last value used for that field and with new value, previous value it generates new line to be added to log. Then it puts this line at the top of that Log field - voila - normally its very fast, so normal user dont know about any logging, but when trigerring from another database file, filemaker crashes..

I was searching this Issues with EventScript, but no one of them solves my problem. I am not using print layout in my database at all and all of my files are named correctly, with just one dot.

Edited by Guest

Hello !

I think your script parameters (here: ID & ¶ & "Type" & ¶ & Self) can be the cause of this problem. I'm not sure but I would suggest you replace the self function. Can you use the actual name of the field instead?

I guess FileMaker can't evaluate the self function while triggering a script and that's maybe why the 1st script step (with Get(ScriptParameter)) is crashing.

HTH.

  • Author

Thanks for advice, that sounded logical, but unfortunately havent fixed the problem :

I already gave up and turned my logging system off.. Maybe in future versions of Filemaker will be this problem fixed.. But actually i dont think filemaker will be fixing bug related to unofficial plugin..

Thanks for help, anyway

Well, my logging system doesnt create any new records at all.. He just works with only Log field .

Then would I not reach out for 3rd party tools at all:

http://www.nightwing.com.au/FileMaker/demos8/demo809.html

--sd

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.