LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how make executable with dataloging and database application in LV8.6

Dear all,

        I have developed datalogging application using Citadel database in LV8.6. My application is running fine in development mode. Now i want to make an executable. I can make executable is fine, but when i tried to run EXE on same PC. I have an error

 

19599iEC3C91DF96FCC7A6

 

In my application, the data from temperature Monitor LakeShore 218 are being acquired via RS-232 port and stored in database(Citadel).

 

While making EXE, it is not showing any error and at the time for running it shows the above error, what mistake i am doing ?

 

--Vishnu

0 Kudos
Message 1 of 6
(2,802 Views)

Vishnu,

 

 If you dynamically call VIs in your application (which it seems that you are from the error message) you need to be aware that the path to these VIs changes when running in the development system and as a built application.  See this link for a description:

http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

 

This may be the cause of your error and should give you an idea how to avoid it.

 

Dan

0 Kudos
Message 2 of 6
(2,783 Views)

Vishnu,

 

Did this solve your problem?  I see that in your next post you seem to be moving forward.  If so, could you please give some Kudos?:)

 

Thanks
Dan

0 Kudos
Message 3 of 6
(2,774 Views)

Dear Berry,

        Thanks and

        Sorry for late reply. Actually i was doing some experiment. But unfortunately i couldn't do.

 

 

I am not able to understand what i have to set in my application as mentioned in document. Here i is screen shot.

 

19717i769119ABAFD10F44

 

Please see it.

This is datalogging application. Log data from RS232 port and display on graph with historical data also.

 

Thanks

 

--Vishnu

 

 

 

0 Kudos
Message 4 of 6
(2,765 Views)

Can you please attach the screenshot and not just embed in the text...it is quite difficult to read.

 

From what I can make out it seems that you are using the "Current VIs Path" function to build the path to the library file.  As mentioned in the link I sent this function will return different paths for running in the development environment vs. executable.  You can create an indicator off of the wire from this function so that you can see what path it is using.

 

Dan

0 Kudos
Message 5 of 6
(2,754 Views)

Dear DBerry,

        Again Sorry for late reply. I have updated my system to LV2009. During upgradation i had problem and My VI is not opening due to some problem. So i finally install LV2009 in new PC and sending you screen shot in Attachment.

 

Thank you very much.

 

With Best Regards

--Vishnu

0 Kudos
Message 6 of 6
(2,717 Views)