Having tested various tools to benchmark a FMS 17 to no avail, I created the attached simple FM test file.
It simply run a script on server or locally, creating records on a loop.
While in local there are no problems, if you load it to FMS it does not create the requested records, without reporting an error.
Anybody can help?
PS: if you load it to your FMS, remember to switch the button to "On Server".
UserName: Admin
Password: 333
Regards
Trevix
Looking at your script it shows that these parts will not work on server. Not sure why but at least we can see why you are not getting the results.
May be it is not clear:
the only script that run on server is the "Crea rec on Server". See line 5>10
Line 11 is local
Looks like you have a spelling error on your script variable named $TotRec. When you declare it, it is spelled correctly but when you pass it as a script parameter on the Perform Script on Server step, you spell it $TorRec. Let us know if that fixes it.
FileMaker Pro 17 Advanced Help
Product | Supported |
FileMaker Pro Advanced | Yes |
FileMaker Go | Yes |
FileMaker WebDirect | Yes |
FileMaker Server | No |
FileMaker Cloud | No |
FileMaker Data API | Yes |
Custom Web Publishing | Yes |
Runtime solution | No |
Yes, there was a spelling error. Sorry.
BUT with the Perform script on server only 6 records get created, instead of...500.
Is like if something stops it, but no error gets reported.
Does it work for, you fixing the misspelled var? Using the "Perform script on server" ?
Thanks for your time but I know the compatibilities.
If you look at the script "Crea rec on Server", it is fully compatible with FMS.
The "Perform script on Server" of FMS does just that: tell FMS to run the script "Crea rec on Server".
I have been using it extensly for Pdf creation, with no problems.
My problem sounds more like a bug
Ciao Roberto,
when you run it on the server, the script Apertura is also run, and it sets the run mode to "locally"... but that's not so important.
I would use Truncate Table instead of Delete all records, but that's also not so important.
I would also get the Commit Records out of the loop, forget about the counter and Exit Loop if Get(FoundCount) > $TotRec.
OK. I found the problem.
Apparently, FM does not understand my vars as numbers (even if introduced as 0 not "0")
Modifying the script as following, everything works, even if it is not exiting (5.000 records in 9 secs)
Boh!
Thanks anyway for helping out
Trevix
Well, is a demo. You must change it manually.
Also, since this will be used to compare different FMS installs, it does not really matter how long it takes.
In case someone find this SpeedTest, useful here it is, in its final version.
Would be nice to receive comments or suggestions.
Regards
Trevix
Forgot to say: FMS 17 on Mac Mini i7 OSX 10.13.6 8GB Ram
What happens is that just 1 record get created by the script that runs on FMS.