I think that is a Bad idea.
An infinitely looping script running as a scheduled event is both redundant and unnecessary. The scheduled operation of the script means you have it run as required and if it fails you can be notified. Its a safe failure mode. An infinite loop that locks up the FMS Script engine can be catastrophic. Its an unsafe failure mode.
I use Server Side Scripts (SSS) for several things, from emails to logging status’s.
They work great, do not overly hog CPU or FMS resources, and if one fails I get an email.
I write the scripts to be ‘self-correcting’ so the next time it runs it picks up records only partially processed.
I would be very interested in why you need such a device....I'll bet that with more details the community could come up with a better solution than an infinitely looping server script.
I agree with ch0c0halic completely. Additionally, though it is a seemingly huge number, there is a real-world limit to iterative processes in FileMaker, and the genuine risk (or likely result) that at some point such a process will simply freeze up when it hits that limit, with who knows what result to the server processes.
I agree with the others; it sounds like an unsafe method of achieving a goal.
But what is the actual goal? What is this script trying to accomplish? I am sure that there are better ways to achieve it...
thats what i said
Yeah, it was a bit of a 'me-too' post (ok...alot), but I did coherently combine both aspects of the thread into a single message!
Also, wanted to reinforce the question back to tntneo in hopes of getting more details.