Newbies llming Posted June 6, 2017 Newbies Posted June 6, 2017 I had tried to install v5.04 into FMS16 but no luck for me.
ryan360Works Posted June 7, 2017 Posted June 7, 2017 Hi llming, We just pushed updates to the plugins to our website. Please download this update and retry. If you continue to have issues, please email [email protected]
Newbies llming Posted June 8, 2017 Author Newbies Posted June 8, 2017 It's work ! Thank you for your work hard.
TobiasViljoen Posted July 4, 2017 Posted July 4, 2017 I have tried every platform, every os, I just can get it to work with Filemaker 16. I have a post on this topic where I will upload new screenshots.
jaylkjr Posted July 15, 2017 Posted July 15, 2017 (edited) I am not certain what is going on but it would seem that FileMaker Server 16 has had multiple issues. I thought 5.04 would fix some issues but it never seemed to work. Version 5.05 works for FMP 16 and FMPA 16 but on FielMaker Server all functions return "?" to the log file for the script. I had thought I had a version working on server but it was completely hanging up when run as a scheduled script. I believe this was recognized as it was cited as the reason for version 5.05. This is a big issue, I think new versions of the plug-in and plug ins generated need to be tested on Windows Server. Edited July 15, 2017 by jaylkjr Correcting missed word
jaylkjr Posted July 15, 2017 Posted July 15, 2017 OK, here is the deal. I think I have figured out some of the issues... When a new version of scriptmaster comes out, it seems you must cut and paste all your functions into the new version FileMaker file. You have to MAKE SURE you put the parameters in the correct order (although you can avoid that by using a let function). After this, you have to insect and make sure that even if the function is named the same, that the scripts recognized it. I don't know the logic as to why some are recognized and others not although the name is the same (cut/paste). It appears that version 5.05 fixes the issue where server side scripts were hanging. We added a timeout to our application for good measure.
Recommended Posts
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