Error when building an executable in BridgeVIEW

[Lupita]

Hi,

Every time I try to build an executable in BridgeVIEW I get an error that I have to close all VIs before building an EXE, but I only  have the top level VI open. I tried shutting down the PC and restarting but nothing works. I have seen this in LabVIEW, but LV closes them for you.

Any ideas?

Thanks.

[Ben]

Did you shut-down the engine?

Ben

[Lupita]

Hi,

I used the Engine Manager to stop and quit the Engine but I keep getting the same error : "The following VIs are in memory. You will need to close them before you can build the application".

Thanks.

[Ben]

You aren't providng many details in your postings so I have to ask dumb questions.

1) Have you closed all of the VI it is complaining about?

Ben

[Lupita]

HI,

You are probably right. So here is what Ive tried:

1) Restarting my PC. Opening a blank new VI and trying to build an application by adding my "main.vi" as a top level VI. This way I make sure there are NO VIs opened.

The list that appears on the Build Application menu contains ALL VIs called by my main.vi.

Thanks again.

[Ben]

BV is so old you are not going to find many people that have it or for that matter even know what it was, so....

To get your question answered, please post a series of screen shots showing us what you are doing in what order because that message should not come up unless you are actually opening the main or antoher VI in memory has those VI's open.

With the pictures others will be able to help out.

Ben

[rolfk]

---

@Lupita wrote:

HI,

You are probably right. So here is what Ive tried:

1) Restarting my PC. Opening a blank new VI and trying to build an application by adding my "main.vi" as a top level VI. This way I make sure there are NO VIs opened.

The list that appears on the Build Application menu contains ALL VIs called by my main.vi.

Thanks again.

---

I can't really say that I remember a behaviour like this but considering that the latest BridgeVIEW version corresponds to LabVIEW 4.1 (which was never released) or so, I would say that this is so long ago that my memory might be flaky here.

And the application builder back then was also not the same as it is now. I'm afraid unless you are going to use a more recent version of LabVIEW together with the DSC Toolkit (which is basically what BridgeVIEW evolved into) there is little cahnge that anybody can help you with this here.

Rolf Kalbermatter

[mrak1]

Hi,

I remember that there were a few issues with the application builder way back in the day.  So, you may have luck if you check out the patches that NI put out for LabVIEW 5.1, BridgeVIEW, and the App Builder. 

Here is a good place to check:

ftp://ftp.ni.com/support/bridgeview/

ftp://ftp.ni.com/support/labview/

Good luck,

Mike

[Lupita]

Hi Mike,

Is there a specific patch/fix that I should look for? None of the files on the ftp links seem to be for the application builder.

Thanks.

[mrak1]

Hi Lupita,

I am sorry but I do not know if there is a patch or not.  However, since the software that you have is so old, the best place to find patches for older software is on NI's FTP site.  There may also be no patch available but it is worth a try to find something.  I will try to help as much as possible but can you provide some more details about your system?

Here are some questions:

• What version of BridgeVIEW are you using?
• What version of Windows are you using?
• Do you have a firewall on your system?
• What are some of the specifics about the machine you are using? (CPU speed, RAM, etc)
• Can you create an executable out of a very simple VI?

Thanks and let me know,

Mike