Help, something happened to my program

Unfortunately, once I've found program corruption like that, there has been no way to recover that individual file. I've typically opened a NEW program file, or blank template file, then started copying the good code into my NEW file. I work my way all the way to the point where I see the corruption and perform a save then file/save-as. In the save-as copy I would continue attempting to copy/paste code from the broken file into my save-as copy. If the corruption appears because of something I've now copied, I note what information I was copy/pasting. I will return to my 'good' saved copy and restart the copy/paste process, then when I make it back to the point where it last broke, I would repeat my save then file/save-as. Either I will long hand rebuild the features from there, or I will re-attempt to copy/paste smaller batches of code to weed out where the corruption is.

Hope it's not too much of a pain to duplicate for you.

Hello,

I think you can try the following

1.) please try this:
open a new empty program,
and copy the broken places into the new program, but command by command, maybe you can mark them correctly with [ctrl->left click]. Start with the last one
if it looks good in the new program, copy it back into the actual program.

2.) try to copy the damaged areas with a pattern offset (just copy with no shifting or rotation so that the new names are created)

3.) delete all the bad parts and rewrite them

4.) delete the whole program and make it completely new

This is an error in the internal composition of the measurement program,
the reasons for this can be varied and can no longer be reconstructed.

I'm afraid you'll have to cut it out like cancer​

Hi,

Thanks for the answers, the problem is solved now by accident.

I opened the partly deleted program (where I couldn't move to the last line) later today with a different probe in the arm, and mistakenly hit 'yes' instead of 'cancel' when the new probe popup window opened. So the program insserted a new probe-line to the end, and after that the copy/paste worked properly with the broken parts

Because of audit requirements, we were required to identify and document anytime a measurement program was altered for any reason. This required appending to measurement program filenames, a version number like v1.2-8 for example. This turn out to be a blessing in disguise as we were also experiencing inexplicable corruption of measurement programs rendering them unusable. To solve this issue, we started putting a copy of the current version being used in an archive folder.

Fortunately for us the latest revision program is stored in doc control and we can always pull out the latest revision if a program gets corrupted. When editing any program before saving it to doc control I always do a "save as" and keep both updated every 10 minutes or so just in case the DEMON raises its ugly head and crashes.

You also have the .PRG~ and .PRG^ that you can rename as the .PRG if the program gets corrupted.