Version 10.0v3 breaks ActiveX support
Description of the issue
I had some VB.NET code that uses the FMP ActiveX interface, that was working fine under 10.0. But then I installed version 10.0v3 update and it removed all of the registry entries for the ActiveX components so now it cannot use FileMaker Pro through ActiveX anymore. Any chance of this getting fixed, or a workaround? FileMaker Product(s) involved:FileMaker Pro 10.0v1FileMaker Pro 10.0v3Operating System(s) involved:Microsoft Windows 7, Windows XPDetailed description of the issue:I have a VB.NET application that uses ActiveX to run scripts in FileMaker Pro. Following the instructions outlined in this web page: http://www.filemaker.com/help/html/create_script.12.12.htmlThis works fine when FileMaker Pro version 10.0v1 is installed on my PC. But when my client upgraded to version 10.0v3, it stopped working, and they get an error saying “Cannot Create ActiveX Component”. I can reproduce the problem consistently, from a freshly installed PC, by following these steps...Exact steps to reproduce the issue:1. Install FileMaker Pro 10.0v12. Create an external application that uses the ActiveX interface to FileMaker Pro.3. Verify that it works with FileMaker Pro 10.0v1.4. Upgrade to FileMaker Pro 10.0v35. Run the external application again, and it will fail on the CreateObject("FMPRO.application") line.Expected Result:The functionality should be the same as in version 10.0v1 Actual Result:An error occurs.Exact text of any error message(s) that appeared:Cannot Create ActiveX Component Any additional configuration information/troubleshooting that is relevant to the issue:I looked in the registry after 10.0v1 was installed, and observed the registry entries for the FileMaker Pro ActiveX components. After upgrading to 10.0v3, those entries were no longer there. For example, the HKEY_CLASSES_ROOT\FMPro.Application registry key was there after installing FileMaker Pro from the CD, but was removed after upgrading to version 10.0v3. Any workarounds that you have found:I have advised my client to re-install FileMaker Pro from the original CD, and NOT to apply the 10.0v3 update for now.