LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to Add New Parameter in Cluster with LabVIEW Executable Program?

    In this VI,it can write the parameter in Cluster to the database (Access 2003).it run well.

    But When I add another parameter in Cluster,such as EE,I have to modify this Cluster. And at the same time,I have to modiy the database (I should add a column of EE).if this vi build to exe, how can I achieve it?Can LabVIEW have any way to increase new parameter EE in Cluster and in Database in executable program?

    Would you give me some advice?Thank you

Download All
0 Kudos
Message 1 of 4
(2,776 Views)

No there is no way to have datatypes or VIs modified in an executable.

 

LabVIEW compiles everything before executing and puts the compiled bits into the built executable. And the executable runtime has no compiler, or edit functionality either. Also if LabVIEW would try to modify it's executables once build, any virus check program that is at least worth its name would yell loud about suspicious activities.

 

If you need to do dynamic database access, you will have to use the database Toolkit accordingly, accesssing lower level funcitons that take the SQL syntax strings, and building those strings at runtime in your application.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 2 of 4
(2,771 Views)
If the executable program can not increase and decrease, can it achive the function by hidden. For instance, in the edit state there are ten variables, normally it display three variables. In this way, can increase seven variables to display?
0 Kudos
Message 3 of 4
(2,759 Views)

It's rather unclear what you try to do here. In your first post you talk IMHO about the high level Datatbase Toolkit functions that take a cluster and translate it automagically into the appropriate SQL Query/Update.

 

Your second question seems to be about the user interface of your application.

 

Proper application design would mean to separate the user interface aspect from the actual database query in some ways. I definitely wouldn't use the same cluster for both. Also if you simply hide a control on the frontpanel (possible also in an executable) it still is present logically and if you end up using the high level database toolkit functions with that cluster it will result into a query or update of the database with all the data in the cluster, also the hidden ones.

 

 

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 4 of 4
(2,748 Views)