Having recently upgraded from Windows 7 to 10 and FTView SE from version 8 to 12, I encountered an issue with Common_AnalogEdit not being able to load Active X due to the presence of Microsoft Forms 2.0 TextBox. If you have experienced a similar problem, I would greatly appreciate your assistance. A screenshot has been attached for reference. Thank you in advance for your help. Regards, MJ Lebotse
To ensure compatibility and functionality, transfer the textbox DLL and any related files, such as an OCX, from the system32 directory to your new computer and re-register them. This procedure is commonly required when updating RSView32 on newer Windows operating systems, which may include outdated versions of the Forms DLLs.
Hey MJ Lebotse, I faced a similar issue when upgrading. It seems like this problem might be connected to how Windows 10 handles Active X controls and Microsoft Forms differently than Windows 7. One potential solution I found was to reinstall or repair the Microsoft Office installation on your machine. The Forms 2.0 library is part of this and reinstalling might help freshen up those dependencies. Also, you might need to adjust your security settings to permit Active X controls to load properly. I hope this helps!
Hey MJ, I faced a similar problem when I upgraded my system, and it was indeed tied to the compatibility with ActiveX controls. One quick fix that worked for me was to ensure that all necessary components were properly registered in the Windows Registry after the upgrade. I also found it helpful to run FTView SE as an administrator. If those steps don’t resolve the issue, consider reinstalling the Microsoft Forms library—it can often get messed up during version upgrades. Hope this helps!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: After upgrading to Windows 10 and FTView SE version 12, users may face an issue with the Common_AnalogEdit Active X control not loading due to conflicts with the Microsoft Forms 2.0 TextBox.
Answer: To resolve the issue, one possible solution is to address the conflict with the Microsoft Forms 2.0 TextBox. Troubleshooting steps may involve adjusting settings, updating software components, or seeking assistance from Rockwell Automation support.
Answer: While specific workarounds may vary depending on the system configuration, some users have reported success by modifying settings or configurations related to the Microsoft Forms 2.0 TextBox. Collaborating with other users who have faced similar challenges can also provide valuable insights.
Answer: If you are unable to resolve the issue independently, it is recommended to reach out to Rockwell Automation's technical support team for expert guidance
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.