I have a development machine that has an installation of Visual Studio 6.0. I was tinkering about in LabView with an ActiveX control to call the MS Common Dialogs, in particular the FileOpen and FileSave dialogs, with more control over filtering (as a sometime replacement for the LV FileDialog vi). MS Common Dialog utilizes the ocx control "comdlg32.ocx". The vi worked great on my development machine. I brought the vi over to a different machine that has a copy of this ocx (and the dll's etc) in what appears to be the appropriate places, but the vi now returns an error, that the Class is not licensed for use.
I've been searching for solutions to this apparent licensing problem all day. I'm not sure, but it appears that there is something that installing VB does to enable the "design time" version of the active X control instead of the "runtime" version of the control, which leads to the question, which version does LabView see? I'm able to see and create automation references to this library on the machine where it doesn't work, and in fact a number of other activeX controls chosen at random returned the same error. I've looked everywhere for a clue - the registry, security settings, properties, version differences, but nothing obvious has shown up.
There was a reference in one place on MSDN to a license pack - but I can't find any evidence that I've got a license pack on the machine that works. Has anyone come across this error? Is it an actual license issue on the MS side or a activeX issue or a LabView issue?