The ScriptMaster plugin does not appear to work on FMS12. Using 4.131. Same plugin, same setup working fine on FMS11. Works great on FMPA12

I am guessing that this is due to the new separate processes in 12 and that 360 Works know about this and a new version, along with some new modules (bar codes) will be released real soon!

Maybe spoke too soon - the problem could have been that the opening script is no lounger called from Server 12 - thanks 360 Works for your email!

Ok - I've done some testing on this lovely Easter Sunday. In all cases below, I've attempted to create plug-ins for both Mac & WIndows at the same time.

For reference, I've done this under Mac OS X 10.7.3 and Windows 7 SP1. Here's what I can report so far:

1) Creation on Mac: plug-in creation fails if you want the plug-in created on the Desktop. By fail I mean it hangs FileMaker Pro 12 indefinitely. Using any other folder seems to work.

2) Registering the plug-in on Mac: Attempting to register it using the automatically generated code in the Preferences dialog causes FileMaker to, again, hang indefinitely. After force quitting (Mac) and re-opening FileMaker 12, the plug-in is properly registered.

3) Creation on Windows 7: plug-in creation fails if you want the plug-in created on the Desktop. By fail I mean it tells you it can't find certain libraries. So far I've not been able to get this to work at all.

Another, more important issue has also arisen. FileMaker, starting in version 11, had a method to load plug-ins in a folder other than the FileMaker application folder. On Mac, this was ~/Library/Application Support/FileMaker/ - I don't recall what it is on Windows. The problem is this: FileMaker 11 and 12 both read the same directory, so you have to manually disable the incompatible plug-ins.

I hope someone from 360Works can comment on the ScriptMaster issue.

Thanks,

--

Michael Frankel

FileMaker Certified Developer

Wizard Consulting Group

Office: (818) 706-8877

Skype-In: (818) 483-4686

Mobile: (310) 291-3419

Skype: michaelfrankel

Website: www.wizardconsultinggroup.com

This appears to be resolved by making sure the ScriptMaster plugin is installed in only one of the two directories (autoupdate or application > extensions).