ECN-4390 Support for older ActiveX controls

In extend 10.0.0, some older ActiveX controls are no longer working as expected; this is the result of Data Execution Prevention, which was enabled in this version.

Data Execution Prevention (DEP) is a Microsoft security feature that monitors and protects certain pages or regions of memory, preventing them from executing (usually malicious) code.

When DEP is enabled, all data regions are marked as non-executable by default.

When DEP is disabled, vulnerabilities such as buffer overruns can leave your code exposed to an injection of malicious code within these regions, which can then be executed. For a more detailed explanation of DEP, visit the Microsoft Support site (https://support.microsoft.com/en-us), where you can find various articles on how it works, and how to enable and disable it on a number of platform and applications.

From version 10.0.0 onwards, the ACUCOBOL-GT runtime and acuthin client has DEP enabled. This should not generally cause any adverse effects, but where it might cause problems is when attempting to run ActiveX controls that were designed prior to the introduction of DEP; the effect is that they will most likely produce a memory access violation exception, which if not handled, will crash the application.

To enable you to continue to use these ActiveX controls, we have supplied a runtime and a thin client that allows you to run your applications with DEP disabled. However, be aware that using these executables exposes the risks mentioned above; see DEP-aware Runtime Systems and Thin Clients in the Help for more details.