Measurement Studio for VB6

cancel
Showing results for 
Search instead for 
Did you mean: 

Measurement Studio 6 FDS upgrade corrupted VB

I just received Measurement studio 6 FDS upgrade to replace my measurement Studio Component Works 1.01. After installing it VB was corrupted.

To prove to myself that this was not just a hard disk or other unrelated problem I rebuilt my PC from scratch.

Here is the final spec after rebuild (before installing Measurement Studio)

NT4 sp6a
IE 5.5
MAX 2.2
NI-VISA
NI IVI
NI MXI3 (PXI1011 chassis attached)

MS Visual Studio 6.0 (VB6, C++)
VB6 Service pack 4
MS Visual Source safe 6 + sp6

VB working correctly.

Install Measurement Studio 6 FDS Upgrade.

VB now has a class reference Error when I tried to add ocx components to my tools (See error message in image 1 supplied) [i.e. right click on tools and
select Components.]
When I OK this error I find that my entire list of components have now gone (see second image)

Has anyone seen this problem before or Have I just been sold the wrong package.

Hope I wrong

Graeme
0 Kudos
Message 1 of 4
(3,538 Views)
The problem is probably that you have comcat.dll incorrectly registered. See the Microsoft Knowledge Base article PRB: Class Not Registered Error and Empty Components Dialog for more information and a possible solution to this problem. Please try this and post a reply to let us know if this resolved the issue.

- Elton
0 Kudos
Message 2 of 4
(3,538 Views)
Thanks Elton
This has fixed the problem
I am somewhat alarmed though that installing one of you products caused this dll registry entry to get corrupted.
Could I suggest at least a warning page in the packaging box.

Many thanks for the quick response though

Graeme
0 Kudos
Message 3 of 4
(3,538 Views)
Dear Graeme,

In the 2 years that Measurement Studio 6.0 has been in the market, we have not encountered this particular issue you experienced. But if we had, we would have certainly documented it and provided workarounds for our customers.
It is hard to determine whether Measurement Studio did in fact cause the corruption of the dll registry based on the information you gave us. It is entirely possible that your VB installation was already corrupted but unnoticeably so.
If you would like us to further investigate this issue, please contact support@ni.com with a link to this thread and any other relevant information that would allow us to reproduce this problem.

Best Regards,
Azucena
Measurement Studio
0 Kudos
Message 4 of 4
(3,538 Views)