How to not overwrite an existing file using the "Save Report to File" vi?

[Matthew_Kelton]

While I understand you do not control this, it is beyond idiotic that a company has a policy in place whereas employees are writing "bad" code becuase writing the code properly requires too much work and time to make it through the approval process.  Anyone who cannot see that you are essentially writing new code needs to be re-evaluated.

Off of my soapbox, I do not think you will be able to find a VI for File/Directory Info as it is a LabVIEW primitive and may exist in a DLL somewhere and not as a VI.

In TestStand, however, try this:

RunState.Engine.GetFileInformation("c:\abc.txt").FileExists

It returns true if the file exists, false if it doesn't.  Replace abc.txt with the name of the file.

[tbob]

So your company says you can never write new vi's?  But you can write new TestStand sequences?  What are they smoking?  Do they realize how much time and money is being wasted by their idiotic policy?

[parkerfly]

It's not that we can never write vi's. But it is strongly discouraged, and to get it approved we'd have to not be able to do it in another manner.  Can you say Dilbert? 🙂

[Dragon64]

Hi:

     Is your company one of those which require Security Clearance or your products are Life threatening if they have bugs? If they are, they must double check and require approval even for the slightest change, but if not, they're stopping their people to do real improvements to their products. And so, their competitiveness in the market share.