Thank you for the response, I will try that.
Regards
Tobie
Feedback : I am in the process of replacing the 64 bit JRE with 32 bit JRE.
Does this imply that one can only run the one and not the other ?
i.e Script master Only in FMPA 15 and FMPA 16 in 32bit if C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 contains the 32 JRE
then it won't work in FMPA 15 and FMPA 16 in 64 bit untill C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 contains the 64 JRE
Will normal Java 32 AND 64 installation be recognised ? and the C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 be ignored ? (or can be deleted ?)
Now testing.......
I found that renaming old (64) C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121_64
and adding the 32 at C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121
actually worked FMPA 15 /32 opens, FMPA 16/32 opens AND FMPA 16/64 opens.
For a variety of reasons , among which, under certain circumstance Pervasive 10 ODBC masquerades as 64 bit while it is actually 32 bit and the DSN's can only be seen as 64 bit, I need both 32 and 64 bit versions.
It's working, I shall not dig any further, I have an update to get on with.
Thank you, I hope this post helps some-one else too !
Tobie
FMPA 16 32 stopped working again. Back to drawing board.
Final finding :
(SWOPPING THEM OUT,
32bit = C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 contains the 32 JRE
64bit = C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 contains the 64 JRE and then ...
Running ScriptMaster 16+.fmp12 from FMS16 (Mac) FileMaker 16 (32 or 64) will fail at first, but one has to to enable the plug-in in preferences every time,
then re-run Startup Script then it works for either 32 or 64)