Jorge Moreno

Thanks for your comments Val and Rolfk, from what you mentioned both I did before some of your recommendations and still did not work, in your case Rolfk I had error handling but not at the startup or Top VI, I added that this morning and I got the following error displayed in the error cluster: "Error loading type library/DLL" The problem resides in that I did not know the nature of the Activex object I was using, I am developing an application and R&D Engineers from other site did not want to share information about the interface controlled by this Activex nor the Activex itself due to security policies from their group, so I had to find out myself how to access these methods and properties to develop a Test Platform for a new product. After browsing for info on this error I found two useful links which I am attaching below: http://digital.ni.com/public.nsf/websearch...EC?OpenDocument http://digital.ni.com/public.nsf/websearch...7A?OpenDocument In my case the Activex object turn out to be an Activex Server instead a .OCX, when I tried to use rgsvr32 to register it as a .OCX I got the following error: ...\ActivexObjectName.exe was loaded, but the DLLUnregisterServer entry point was not found ...\ActivexObjectName.exe does not appear to be a .DLL or .OCX file. After reading from the knowledge base at NI how to register an Activex Server then I did: ...\ActivexObjectName.exe /RegServer And it worked!!!!! I hope this help help other with similar problems than my application Thanks Jorge Moreno

Hi all, I have a problem with an external code developed in VB 6.0, I am accesing it from Labview 8.20 using the "Automation Open" to have access to properties and methods, the code works just fine in development environment and if the executable build is ran in the same laptop I use for the development. The problem shows when I try to run my labview code in a different machine, I have created the same directory structures to avoid any problem related to location of the right activex, in fact you can see that the Labview .exe applicatioon is actually calling the activex object because is opened but when it's supossed to execute several methods within these activex it does not do anything, I have realized that because the main function of the activex should be to Open the Com Port, I have Serial Monitor software spying the Com Port activity and does not do anything. Any idea why it works as .exe in the laptop where I developed and not in a different machine. PD The Laptop has Windows Vista Enterprise and the PC where I want this to work is an XP Pro Thanks for any help I am sure it should be a minor detail I am no seeing