DLL Loading Error

[Novatronics]

I created my application which works well on the test stand but would also like to run my application on remote computers in report mode only (no test hardware present).  The test stand saves all data in a database and I would like the ability to reload data from other computers that do not have the hardware.

The problem I am having is that LabView is trying to open the dll’s for hardware that is not present on remote computers and causing an error.  How can I get LabView to not open dll’s or ignore the errors?

Attached for your reference is one of the VI’s that invoke a dll.

Thank you,

Paul

[Dennis_Knutson]

You've found one of the better reasons to upgrade to LabVIEW 8. LabVIEW 8 has the conditional and diagram disable structure. Code inside one of these is not checked for errors or compiled. If you don't upgrade, you can install the DLLs with no hardware, or make all of the VIs that access the DLLs, called dynamically. Dynamically called VIs are not compiled until loaded so if you don't load them in report mode, you won't get any errors.

[Novatronics]

Thank you for your response.  I have a couple of follow-up questions.

1. With LabView 8.0 is the conditional case control programmatically or is this a manual process?

2. With respect to your second comment “Dynamically called VIs are not compiled until loaded so if you don't load them in report mode, you won't get any errors.”  I thought the dll’s would not be loaded as well but when LabVIEW loads the project it gives these errors prior to even running the project.  The dll’s are on the computer that I am testing this problem with and I do not fully understand what is happening.  The exact error is: Error loading xxxx.dll A dynamic link library (DLL) initialization Routine Failed.

Thanks for any comments,

Paul

[Dennis_Knutson]

You can set options in a LabVIEW project for the conditional disable structure. You could have separate projects - one for hardware and one not. The actual VI where you use it would not change.

You might want to check the dependencies for the DLLs that you call. If a DLL requires another DLL and that is missing, you'll get that error.