Jump 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.

Server Side Scripting Bug

Featured Replies

[7:27:56 PM] Robert Schaub says: Today I discovered and reported to FileMaker as a bug

In FileMake 9 Server , you can now shedule the server to run a script inside any file.

Good So far..

Here's the bug

Loop

Perform Script [Your Script Name]

Go To Record [Next] [Exit After Last]

End Loop

The result ends in an error when it reaches the End Loop

The error is 101 Missing Record.

This causes the server side script to crash and any others after it will not be run.

The Work Around after hours of experimenting

Loop

Perform Script [Your Script Name]

Go To Record [Next] [Exit After Last]

Exit Loop If [Get(RecordNumber) = Get(FoundCount)

End Loop

After the last record it exits loop and the end loop is never executed, therefore the

101 error message is never reported and live goes on.

Those of you with a script debugger try it and click on the option pause at error.

Which version of FileMaker Server 9 is this? Is it 9.0v3? Also, what is the exact version of the OS on the machine running FMS9?

Steven

  • Author

Hi Steven,

The servers 9.v3 are on Macs 10.4.x i believe

Clients use XP with either Advanced or Pro

Try creating the script I posted above and Use the Debugger with pause at error option on.

After exiting from last record and hitting the end loop statement it returns the 101 Missing Record error.

When you run this as a scheduled script on a server the script stops and you get an email message that it failed. I now think this also causes the server to max out on memory and the server must be restarted.

  • 1 year later...

Thanks for the fix. It's still present in FM10 server, which is quite annoying.

  • 2 years later...
  • Newbies

I can confirm the behavior is still present in FMSA 11 as well. Also chopper's workaround is slightly flawed. As written it will never perform the desired script steps on the last record. The order should be instead:

Loop

Perform Script [Your Script Name]

Exit Loop If [Get(RecordNumber) = Get(FoundCount)

Go To Record [Next] [Exit After Last]

End Loop

Have you tried this with Allow User Abort [ Off ] and/or Set Error Capture [ On ] ?

Create an account or sign in to comment

Important Information

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

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.