Robert Schaub Posted April 30, 2008 Share Posted April 30, 2008 [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. Link to comment Share on other sites More sharing options...
Steven H. Blackwell Posted May 1, 2008 Share Posted May 1, 2008 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 Link to comment Share on other sites More sharing options...
Robert Schaub Posted May 1, 2008 Author Share Posted May 1, 2008 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. Link to comment Share on other sites More sharing options...
bobthedog Posted June 11, 2009 Share Posted June 11, 2009 Thanks for the fix. It's still present in FM10 server, which is quite annoying. Link to comment Share on other sites More sharing options...
Newbies ron_hesse Posted October 10, 2011 Newbies Share Posted October 10, 2011 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 Link to comment Share on other sites More sharing options...
Fitch Posted October 11, 2011 Share Posted October 11, 2011 Have you tried this with Allow User Abort [ Off ] and/or Set Error Capture [ On ] ? Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 4605 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now