Writing data infrequently without data breaks?

[toddho]

I have an application that I need to programmability write a single data point once every week or month.  If I open up a data trace and write to it and then close the trace I also get a data break added automatically.  This data break makes viewing that trace in Measurement and Automation Explorer impossible.  Any ideas on how to write this data without keeping the vi open for a month to write only a few data points?

Thanks

Todd

[Joel-P]

Hello Todd,

Have you thought about simply saving this data to a file and then appending to that file each time that this code runs?

With regards to not running the VI continuously for weeks or months, we should have very minimal processor usage if we have the code check time once every minute/hour and then acquire data after X period of time. We can also consider building this code into an executable and create a basic task with the Windows Task Scheduler to run that executable every day or so.

Cheers,

Joel

[toddho]

Thanks for the reply.

To be consistent with our organization I need to place that data into the Citadel database AND view it with MAX.  The problem with running an executable once a month is that the trace will open and close each time I run the exe.  This will place data breaks into the data.  I have thought about opening the trace, writing the data (with the data break), reading ALL the data back out removing the data breaks, deleting the trace from the database and then recreating the trace and writing the data I just read out back into the "new" trace each time I write a single data point.  Cheesy workaround but that's all I've got right now!?