LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

file path problem

The key in this case is definitel whether you are in development mode or exe.

 

To which I say, follow my logic above so that you don't care.  Treat them both the same. 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 11 of 13
(686 Views)

My concern with llb's is that if it gets corrupted, everything gets corrupted. They were originally created to give the original Windows LabVIEW users, back in v2.5, the ability to use long vi names, back when Windows was limited to 8.3 filenames. I have avoided them for quite a while, have lost a whole days work on a few occasions when a hiccup corrupted the file. It isn't as likely now, CoastalMaineBird's technique would definitely resolve the immediate issue, by artificially putting that extra file level in.

 

 

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 12 of 13
(674 Views)

Hi

   See in case current file path is taken into consideration,there should be a change in file path correction at the time of coding and at the time of builiding EXE, even i faced the same problem at the begining and some minor changes in fila path handling at the both instant. 

Kindly look through the following attachment.

 

Regards

Visuman

0 Kudos
Message 13 of 13
(670 Views)