I've been battling with an Active X control for a while now. Everytime I use a particular active x control inside a VI, it crashes during execution. Labview wasn't giving much of a hint, but after an exhaustive investigation, we determined that the exe must be in the third party vendors bin folder for it to work properly. In other words, the active x control looks for lower level dll's using the executable's relative path. I've successfully got this working by building an exe from Labview and then placing it in the bin folder and executing from there.
So my question: Is there anyway to get this working correctly in the development evironment? Right now, if I try to run this from the development environment, it looks for the dll's relative to the path of Labview.exe. Is there any setting to make a VI look like it is running from a different location? I know I could continually create builds, but it would be much easier if I could run VIs from the development environment while I develop and debug.
