A
|
ann 6/2/2010 |
Hi, |
M
|
mfred author 6/2/2010 |
I should have made a copy of the corrupted file before I figured out one way to fix it. I was creating the application in 6.2 but I had not removed 6.1 yet. Since I was in a crunch for time, I tried opening the 6.2 file in 6.1, saving it then reopening it in 6.2. I lost some design changes but most of the work was salvaged this way. I probably lost an hour or so of work instead of 5 or so hours. |
M
|
mfred author 6/2/2010 |
This just happened again. I am emailing the project. |
M
|
mfred author 6/2/2010 |
I figured out what was corrupted in the file. I changed the extension to .txt so that I could look at the code in the .aspr. Fortunately, I saved a copy of the file this morning, before I started working on the project again. I compared the code of both files and noticed that the old file ended with </project> but the corrupted file with all the changes did not. It took a while but I found where the code abruptly ended in the corrupted file. I pasted the hundreds of lines of missing code and saved it. Worse case, it wouldn't work and I would have to use the 6.1 method that I previously used (although I still don't know why 6.1 didn't see it as a corrupted file since it was missing so much code. Well, I opened the file in 6.2 and everything appears good. |