hexagon logo

Program died after 3 days of work

Solved-->

My IT Dept helped us recover backup files that were deleted and then Matt explained to me what they were and how to recover using them & we did so successfully. I never fully understood what those temp files were and have been deleting them as I go all of these years. I finished the program, deleted the temp files as I always do, then went "oh crap I need to delete this one case statement", did the deletion, then BOOM chaos lmao

Matt's words:

"Thanks for allowing me to remote in. As discussed, I copied the program backups (~ or ^) and put them in a directory that had the .CAD file. I removed the character at the end, so it reverts to a typical .PRG file and then we could open the program. "


__________________________________________________ __________________________________________________ __________________________________

Original Post-->

Spent three days writing a program. Deleted a CASE statement.

All of a sudden...STACKDUMP

Now, program refuses to open and says "Attempted to access an unnamed file past its end." followed by "PROGRAM_NAME.PRG (Schema:0) Serialization error ALT" followed by "Error: File closed because of bad archive"

Do I usually back up my programs 8x per day? Yes, I do, however for some god awful reason my dumb @ss had this file saved on my desktop and was working from there...so Alwayssync did NOT back this one up. Lesson learned.

Oh and by the way I forgot to mention that my Purchasing Dept dropped the ball on sending out my SMA payment on time (due 12/31 so now I am technically expired) so the Hexagon Software Support Dept is having a spasm trying to figure out if they can still help me with a pending/unprocessed PO or not....lololConfusedRolling eyesSunglassesSunglassesSunglasses

Anyone have any advise? Or should I just re-write this program? PCD2021.2 (release) CAD
Parents
  • Been there! I've had this happen when a larger program gets modified too much. If I am working on a larger program, I will save as... and add a v# at the end (for version number. Replace # with an integer) between each save. So if that one gets corrupted, I have a previous version of the program saved I can add to.

    Sometimes the .PRG^ and .PRG~ are hit-or-miss depending on save repetitions.


    I do the same thing with big programs. It even helps with being able to go back to earlier edits of a program if something gets really messed up with an alignment or something.
Reply
  • Been there! I've had this happen when a larger program gets modified too much. If I am working on a larger program, I will save as... and add a v# at the end (for version number. Replace # with an integer) between each save. So if that one gets corrupted, I have a previous version of the program saved I can add to.

    Sometimes the .PRG^ and .PRG~ are hit-or-miss depending on save repetitions.


    I do the same thing with big programs. It even helps with being able to go back to earlier edits of a program if something gets really messed up with an alignment or something.
Children
No Data