AnsweredAssumed Answered

Need help writing code to stop 16.0.1 or 16.0.2 users from accessing our organizations databases

Question asked by on Oct 13, 2017
Latest reply on Oct 16, 2017 by

We have more than 100 deployed FM databases that are critical to the day to day operation of our organization.  Recently one of our FMP 16.0.1 users suffered a serious data corruption (twice) without explanation.  I've never seen anything like it.  Shortly thereafter FM offered 16.0.3 to correct a bug that explained the data corruption.


I wrote some script steps using the get(ApplicationVersion) calculation to be inserted into our more than 100 solutions in the ON FIRST WINDOW OPEN script, tested it, and it worked for me (using 16.0.2/Mac/Sierra) but others with 16.0.1 or 16.0.2 could still get in.  Not good.


I need some help writing a bullet proof bit of code the prohibits 16.0.1 and 16.0.2 FMP, FMP Advanced and FMGO users from logging into a hosted solution across our organization.


It needs to be elegant, simple and durable (lasts for years).


Can you help?