Possible Cause #1
If you are using our ActiveX controls in Visual Basic, and you are receiving errors (such as: "DAX ERROR Access violation at address 037760C2 in module ‘isAnalogLibrary.ocx’ write of address 0A94D0C0." or something similar) when you open, close, or edit a form, then you may be running into a property streaming issue with our older ActiveX components. This issue has been resolved with our Service Pack 5 and higher releases.
To correct this problem, do the following...
- Install Service Pack 5 or higher (you can find our latest service pack here)
- Open your VB project and either move a control on the form or change a property of one of the controls on all forms that use our controls (this forces VB to re-write the corresponding FRX file)
- Save the VB project
- Close and re-open the VB project and the errors should cease.
If this doesn't resolve your problem, please contact technical support and we will instruct you on how to manually edit the FRM file or we can repair them for you.
Possible Cause #2
A bug was been discovered in our ActiveX components (versions 1.0.0 - 1.1.4 SP6) with regards to some infrequent DAX errors in Visual Basic running under all versions of 32-bit Windows. This issue only occurs when...
- You are using components from multiple numbers of our libraries.
- You are running your program in the design environment (not running the compiled application).
- You sometimes receive a DAX error when closing the program several times during one Visual Basic development environment session.
- The error would occur when closing your program and returning to the Visual Basic designer.
We have confirmed this to be a problem. Please upgrade to Service Pack 7 and higher to fix this problem, this is a free update.
Possible Cause #3
A bug was been discovered in our ActiveX components (versions 1.0.0 - 1.1.4 SP6) with regards to Visual Basic 5-6 crashing when using MDI forms under Windows 95/98/ME. The issue occurs when you have two modeless dialogs in a MDI form with one form containing at least one of our components, and you maximize and restore the dialogs.
We have confirmed this to be a problem. Please upgrade to Service Pack 7 and higher to fix this problem, this is a free update.
Possible Cause #4
A bug was been discovered in our ActiveX components (version 2.0) with regards to using theme Panel in Visual Basic 5-6 running under Windows 95/98/ME. This issue has been fixed in our latest release. To obtain this release simply re-run your One-Click Installer that was provided to you (small 200KB file) or contact Iocomp Software for a new copy of your Full Product Installer (6MB download). This issue does not affect CD-ROM distributions of our Version 2.0 product.
Copyright ©1998-2007 Iocomp Software Incorporated. Iocomp and the Iocomp Logo are registered trademarks of Iocomp Software Inc. All other trademarks are registered by their respective owners.