LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Parallel access of database

I need to have parallel access to a database from two different application.

The first application is a TestStand program that will open this database and then write into the database. This open and write process will occur continuously as new data are needed to be logged inside the database.

The second application is a VI that will fetch data from this database. This VI will open the database and read data from it. This VI will also run continuously as it attempts to extract any new data entered into the database.
As you can see, there is a potential problem. MS Access allows only one access at any time and therefore for my two applications to open and access the database at the same time has been causing me problems.

I have tried o
pening the database and then freeing the database after every data entry but still it won't work very well.

Any suggestion on the best method to go about doing this? I only intend to use LabVIEW features. I'm using especially the database connectivity toolkit. Thanks for any help.

Sincerely
Parker
0 Kudos
Message 1 of 3
(2,518 Views)
This thread is continued here:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000D9D70000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
0 Kudos
Message 2 of 3
(2,518 Views)
Another approach could use a functional global vi that controls reading and writing the database inside a single vi. Select the write mode and pass data to the functional global. Select the read mode and get data out of the functional global. Only one mode can be activated at a time inside the functional global. Could you use the Citadel database and memory tags inside the DSC tag engine?? I ran into some file size limitations using the MS Access and database connectivity method at around 2GB on win2000.
0 Kudos
Message 3 of 3
(2,518 Views)