error running application

[srini]

I made a .exe file of my VI. When I run the application in another PC where LV is not installed, I get the following error:
Error loading <my VI name>.vi. LabVIEW error code :21 some external subroutine cannot be loaded
I am using LV7.0 AND Win98 OS. Can anyone help me to sort out this problem?

Regards,
Srini.

[Dennis_Knutson]

You've got something missing. It could be a hardware driver (NI-DAQ, NI-GPIB, etc.) or any other number of external DLLs. A little more information on what your VI is doing and what functions is has could help narrow down the problem.

[michenglaoxu]

Try to built up a installer to see if the problem still exists. If it still exists, double check you own VI' path (developement mode or running mode).

[srini]

About my VI:
    The VI will acquire data from my custom built PCI DAQ card. I have written my driver in C and made a DLL using Visual C++ 6.0. Then the rest of the part does processing of the acquired data and report generation, displaying on the front panel stuff. I have a few DLLs for processing the acquired data and few SubVIs also. This is about my VI in nutshell.
    I have made sure I have included all SubVIs and DLLs when building the application. Actually I was trying to install LabVIEW and run my VI on the PC in which the application was not running. But when I am opeing the VI, I am getting the message, " <dll name>.dll is not a 32-bit dll ". So, the DLLs are not getting loaded and my VI is also not running in that PC. Surprisingly, this message does not come for all DLL files I am using in my VI. So, I think there may be some problem associated with my DLLs and it is not able to load them when my application starts. Can you get any hint after reading this? Plz let me know what can be done.

Regards,
Srini.

[srini]

I have built an installer, installed it and then tried to open the application, but the problem persists. I didn't get how to check whether my VI is in running mode or development mode. Could you please make it clear?

[Dennis_Knutson]

It's likely that a called DLL is not in the expected location or that a dependent DLL is not present or in the expected location. You may want to run a dependency check on the DLL you wrote and see what it calls.

[srini]

Could you please let me know how to run dependency check on my DLL.

Regards,
Srini.