| Author |
 Topic  |
|
|
hainesbe
3 Posts |
 Posted - 21 Jul 2005 : 15:05:26
|
I'm getting the following error message on run in Visual Basic 6.0, service pack 6:
Class not registered.
Looking for object with CLSID:{ECCBA8A5-1F6D-11CF-B697-0020AFEB10A0}
VB6sp6 is running on a WindowsXP, service pack 2 platform.
I believe the error is related to the use of the RTPIDX control in conjunction with another third-party ActiveX control as described below.
All ActiveX controls in the WINAXC200200R1x0x728x3 software package were properly registered at install time as described in the README file.
I am able to compile the PID example program without error.
I am using additional third-party ActiveX controls in my program, which are also properly registered at design time. The example programs from this source compile without error.
The above error only occurs when both third-party ActiveX controls are used in the same program.
Any thoughts on this?
B. |
|
|
quinncurtis
1164 Posts |
Posted - 21 Jul 2005 : 15:13:23
|
Sorry, but we do not know the cause of the problem.
What is the name of the other ActiveX control involved in the error?
When you add that control to our PID example program, does the problem reproduce ? |
 |
|
|
hainesbe
3 Posts |
Posted - 21 Jul 2005 : 15:30:40
|
The second ActiveX control is published by Data Translation, Inc. as part of their software package DTx-EZ. It is available for free download at the following website:
http://www.datx.com/datx/products_pricing/prod_DTx-EZ.jsp
I am using the RTAcq32.ocx control to get/put data to a Data Translation A/D card.
The error persists if the Q-C control is placed in the DT 'single value' example (Sv.vbp) and vice-versa.
Is it possible for the controls to interfere with each other?
B. |
|
|
|
quinncurtis
1164 Posts |
Posted - 21 Jul 2005 : 16:35:29
|
We downloaded the DT stuff, installed it and were then able to reproduce the problem. We found the DT software was creating a temporary file in the Windows/Temp subdirectory. That led to a flash of brilliance where we surmised that the DT ActiveX controls require, quite erronously in our opinion, that ALL ActiveX controls used in the same program must reside in the Windows/System directory, else it could loose its path to the file in the Windows/temp directory.
Our ActiveX controls are installed and registered from our QCActX/lib directory, and have NO position dependence on where they are installed.
We copied the RTPIDX.ocx to the Windows/System directory and re-registered it there. You can re-register it from the VB Components Dialog by selecting Browse and selecting it from the Add ActiveX Control dialog. That seemed to solve the problem.
|
|
|
|
hainesbe
3 Posts |
Posted - 21 Jul 2005 : 17:54:26
|
Hmmmm....
Your analysis and fix are quite astute. However, I am now running into another problem:
I can copy the RT ActiveX controls in the path you specify, however when I attempt to register the control through the VB dialogues, I get the following error:
The file 'C:\WINDOWS\System32\RTPIDX.ocx' was not registerable as an ActiveX Componet.
When I run regsvr32 manually, I get the following:
LoadLibraray("c:\WINDOWS\System32\RTPIDX.ocx") failed - The specified module could not be found.
??? What ???
I can find it... it's right where I put it!
btw, I have tried placing the .ocx in windows\system path as well, same reults. In addition, I have installed all necessary software on the target machine (as opposed to my development machine) with similar results.
Further assistance is *much* appreciated.
B. |
|
|
|
quinncurtis
1164 Posts |
Posted - 21 Jul 2005 : 19:22:33
|
| If you move or copy any of the RT ActiveX controls your must also copy the support DLLs that we use, WCT32DX.DLL and WRT32DX.DLL, found in the QCActX\Lib directory, to the same directory, so that the ActiveX control can find them. |
|
|
| |
Topic |
|
|
|
RTPIDX compile error, 'Class not registered'
