Offline result to database not report file

[Iamthedudeman00]

Hi my current project requires a fail safe way to store the test results: If there is a network outage the test results on my tester must be stored locally and then later on be able to transfer to the network database(Or transfer to network database first but if fails to do so, back it up locally). I had a look at the Teststand forum on this topic but what makes my case different is that I don't want the teststand result files, i need only to log to database somehow. i have a custom database format which only logs one line of records for each test including test time, serial number, test results. (report files are hard to navigate for the subsequent testers which need to read these results). I had a look at the offline result processing option on Teststand which looks promising but it still appears that it tries to log to tsr(teststand result file) instead of logging into a database. - I am a little confused to how this works. Could you please tell me if the offline result process is the way to go? And if so what is the best way to do it? Thanks a lot.

[~jiggawax~]

SystemLink does this for you.  Not sure if that is an option.  Might be worth looking into.  It will change how you do everything though and is kind of pricey but it is a pretty sweet product from NI.

If it isn't an option then the best solution in my opinion is if your database has some sort of sync framework then utilize that.  Always write to the local DB and then it has something on the backend that looks to the online DB and keeps the databases synched.

TSR files are good for backup.  I use them for on the fly reporting in case of catastrophic circumstances.  If you did the TSR route you could automate the Offliine Results Processign Utility (ORPU) to run a job every night at a certain time or something.  You still run the risk of spotty connection though.  

My thoughts.