06-23-2016 10:00 AM
Does this mean I am screwed?
Solved! Go to Solution.
06-23-2016 10:18 AM
@RTSLVU wrote:Does this mean I am screwed?
The answer depends on if it was backed-up.
If you rename the file you posted as ".xls" it will open in Excel and shows me three tabs ...
Ben
06-23-2016 10:24 AM - edited 06-23-2016 10:25 AM
Oh crap I know what I did, and yes I am screwed because I have no backup
I just aded the "current VI path" constant to the path input so it overworte the VI with the Excel file it created.
06-23-2016 10:37 AM
@RTSLVU wrote:Oh crap I know what I did, and yes I am screwed because I have no backup
...
The only good thing I can say is that you will probably re-write that VI better and faster this time.
Ben
06-23-2016 12:49 PM
HA! I am not so screwed after all, thanks to the internet.
I ran into a problem recreating the lost vi, so I went to the forum post I made on the XLR8 support forum where I had a similar problem.
Lo and behold my vi was there, at least a slightly older version. That saved me some work.
06-24-2016 08:56 AM
Glad you were able to find a backup! You should think about using a form of SCC, it makes life alot easier.
06-24-2016 09:16 AM - edited 06-24-2016 09:17 AM
@SigRob wrote:Glad you were able to find a backup! You should think about using a form of SCC, it makes life alot easier.
Don't even get me started on source control, I don't know what we have here but whatever it is, it will not work with LabVIEW.
As much as the manufacturing test group argued to get a compatible one, our firwmare group flat out refused to consider LabVIEW when they bought the source control software.
06-24-2016 09:24 AM
Corporate must like to live life dangerously, depending on what percentage of your companies code is LabVIEW! If you are ever able to make some headway, or even just set up one for yourself, I use Visual SVN Server (on the server side) and Tortoise SVN (on the client). Super easy to set up, is completely free for the basic versions, and can even integrate into LVCompare.