LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Builder error

After buildung standalone application I got an error that says that one of my subvi is not executable, however development application works fine.
I used Active X for Excel 2000 and work under LV6.0.2 on W2k.
Should I mark "Enable Active x server" in builder options ?
Where is the problem ?
Romek.
0 Kudos
Message 1 of 7
(3,325 Views)
Is the code you're trying to build call any DLLs? A common source for this type of problem is if it can't find a DLL it needs.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 7
(3,325 Views)
Which subVI does it say is not executable? Is it one with ships with LabVIEW or one that you built?
J.R. Allen
0 Kudos
Message 3 of 7
(3,325 Views)
First answers:
Mikeporter - I don't call any DLL's.
JRA - this sub'vi is my own construction, but i use in it Small E-mail.vi and Active X.
I suppose that problem is in Acive X, cause everytime I want to do anything with this subvi (e.g. add a constant or change the connections) the wires connected to Excell 2000 Active X become broken and I have to click onto Excel_Application RefNum and again select Server Active X Class. I save this subvi, and everything is OK until I don't "touch" this subvi again. I thing, that during building standalone this situation had happen again.
Am I right ?
Please comment.
Romek.
0 Kudos
Message 4 of 7
(3,325 Views)
Well it's certainly possible. If you are having that sort of thing going on with the subvi there's something hinky with the installation of Excel on your machine or something. The behaviour you mention is NOT normal. I have used ActiveX to conect to Excel a lot and have not experience what you describe.

Does the Excel control examples that ship with LV exhibit the same behaviour?

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 5 of 7
(3,325 Views)
Thanks for your commitment, but I've found bug in my subvi. It consist of two parts: first - read rows from excel worksheet and return this array and number of first free row in this worksheet, and second - writes to this free row in worksheet a new data.
The problem was in the range of possible value of free row - it could be from 0 to inf. but excel accept range from row no. 1.
During work this value of free row was always over 0, but application builder found that there is possibility of 0 and get an error during compilation.
However, I've add an constant=1 to this value (first free row) and standalone application was build succesfully.
Interesting, isn't it ?
Regards.
Romek.
0 Kudos
Message 6 of 7
(3,325 Views)
This sounds very strange... Mostly because the compiler in LV isn't smart enough to catch the kind of things you talk about. It can't catch runtime error. It depends on your code to do that.

Was this code by any chance written in an earlier version of LV and converted? I have seen problems in te past where an error occurred during conversion and was "fixed" by replacing a control or some other sort of unrelated action like changing wiring.

What version of LV are you working in?

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 7 of 7
(3,325 Views)