LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Non-Executable VI in BridgeVIEW 2.1.1 Runtime

Hello,

We have produced a large BridgeVIEW 2.1.1 application (~ 30 MB). We
are using SCC and the following is our plan to distribute our
application:

1. Retrieve all files from SCC, change the read-only property.
2. Build an Install Shield that will place all of our files into a
single directory on the target machine. Note that this directory
structure is diferent than the development directory structure which
has vi's in many subdirectories based upon their type.

The problem we are having is that after we run the Install Shield on
the target machine, BridgeVIEW 2.1.1 reports that a sub vi is not
executable. When we open the application in development, we notice
that there are many vi's that have a * in
their title bar indicating
that they have changed. Development's change explanations range from
"A sub vi has been found in another directory" to "The vi has been
recompiled from LV 5.1 to LV 5.1.1" We have tried opening individual
vi's but the only ones that do not execute are those that have the
"The vi has be recompiled from LV 5.1 to LV 5.1.1" message. This does
not make sense because all of our computers are running BridgeVIEW
2.1.1 (same as LabVIEW 5.1.1).

Does anyone have any experience with BridgeVIEW 2.1.1 Run Time?

Thanks,

Tim Erickson
Signature Control Systems
0 Kudos
Message 1 of 2
(2,552 Views)
Tim,

This is an all too common problem when building an application to load, and then run non-built VIs - the only real solution to the shortcomings of the app builder.

However, the solution is very simple.

The VIs MUST be in a directory structure that is identical to the target structure. This is because VIs are saved with a location. That is, callers look for their subs in specific locations. When you move these files, you loose 'contact' with it, and the caller becomes unexecutable.

Try rebuilding your development directory structure to match the target, opening all files, and reclosing them to save their paths, and then rebuild your install shield. You should have no problems.
Message 2 of 2
(2,552 Views)