Historically I've just written data to the local hard drive on the test PC to prevent LabVIEW from locking up if the PC happens to lose network connectivity for whatever reason. However, for multiple reasons (redundancy, remote monitoring, etc.) it would be ideal for our test program to be able to write this info to a network drive location.
My question is, what are some Best Practices for accomplishing this? How have you overcome the inevitable loss of network connectivity? Is there a way to have LabVIEW buffer the data while continuing to test and then write it to the network once it has come available again...without freezing up? Are there any existing VIs that can handle this? I don't want to have to re-invent the wheel!
Additionally, it would be really nice if LabVIEW could figure out how to continue writing to a CSV or XLS file even though someone has the file open in another program. I can't even count the number of times I've had a test program crash because I forgot to close out of the datalog file in Excel before re-starting a test...nevermind that I was only LOOKING at the file and made no changes to it.