joemosher
September 22nd, 1999, 10:32 AM
We (at work) have an "intelligent forms designer" which uses the Microsoft DHTML control to display an HTML "web-browser" page in a VB6 form. The form and the HTML control work together to allow us to drop ActiveX controls onto the browser page, and to move them around, add text, view property pages to set properties, etc. Basically, it is a method to allow our users to design their own data entry screens.
This worked fine until we installed IE5. Now when we try to display the property pages while running in the VB6 environment, we get errors and the property page will not display. This makes the project difiicult to debug and is very frustrating.
NOTE - This only happens when both the source code for the project and the source code for the control (and property page) are loaded (by loading the project and then using File | Add Project to load the control). When the project itself is open without the control source code (i.e., the control and property page code is running in "compiled" mode rather than in the environment) then it works OK. We need to be able to run the source code for the OCX in the environment along with the project that uses the OCX in order to debug!
If anyone has any information on how to circumvent or correct this problem, please let me know. Thank you.
- Joe Mosher
This worked fine until we installed IE5. Now when we try to display the property pages while running in the VB6 environment, we get errors and the property page will not display. This makes the project difiicult to debug and is very frustrating.
NOTE - This only happens when both the source code for the project and the source code for the control (and property page) are loaded (by loading the project and then using File | Add Project to load the control). When the project itself is open without the control source code (i.e., the control and property page code is running in "compiled" mode rather than in the environment) then it works OK. We need to be able to run the source code for the OCX in the environment along with the project that uses the OCX in order to debug!
If anyone has any information on how to circumvent or correct this problem, please let me know. Thank you.
- Joe Mosher