Lotus 1-2-3 Version 5 file was modified and now unable to be opened. I heard there was a utlity available to resolve these sorts of problems but I have been searching diligently and haven't found anything (so far). Any advice, thoughts, suggestions would be greatly appreciated (otherwise a restore of an older file is in order and all updates will be lost).
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Lotus 1-2-3 wk4 file corrupt and unable to be opened
- Thread starter Cleo02
- Start date
DaleWatson123321
Programmer
Cleo02,
I'm not aware of the utility you refer to - hopefully others will be aware and respond.
However, in the meantime, I thought you should confirm that the following is NOT the scenario...
...that the file was modified using a LATER version of Lotus 123.
If this IS the case, then I would suggest that your BEST solution is to retrieve the file using the same LATER version - and THEN choose the option in that version to save the file as a "version 5 compatible" file.
Hope this helps.
Regards, ...Dale Watson dwatson@bsi.gov.mb.ca
I'm not aware of the utility you refer to - hopefully others will be aware and respond.
However, in the meantime, I thought you should confirm that the following is NOT the scenario...
...that the file was modified using a LATER version of Lotus 123.
If this IS the case, then I would suggest that your BEST solution is to retrieve the file using the same LATER version - and THEN choose the option in that version to save the file as a "version 5 compatible" file.
Hope this helps.
Regards, ...Dale Watson dwatson@bsi.gov.mb.ca
- Thread starter
- #3
DaleWatson123321
Programmer
Thanks for eliminating that possibility.
I just thought of one more (possibility) to eliminate (or hopefully it might be a solution).
Have you checked out the possibility that the user has been saving the file using "Backup". If so, there's a "slight" possibility that the Backup file is not corrupt.
In using "Backup" (SLASH FILE SAVE ENTER BACKUP), 123 first copies the existing file to a filename with the same prefix, but with BAK as a suffix, then saves the "screen" file as the WK4 file.
To open a BAK file, simply type *.BAK - which will then display all BAK files. If you CAN retrieve the BAK file, it will be because it was NOT backed up WITH the corruption, and therefore will NOT be as recent as the WK4 file. However, it probably will be more recent than your other WK4 backup files.
Here's hoping this will prove successful.
Regards, ...Dale Watson dwatson@bsi.gov.mb.ca
I just thought of one more (possibility) to eliminate (or hopefully it might be a solution).
Have you checked out the possibility that the user has been saving the file using "Backup". If so, there's a "slight" possibility that the Backup file is not corrupt.
In using "Backup" (SLASH FILE SAVE ENTER BACKUP), 123 first copies the existing file to a filename with the same prefix, but with BAK as a suffix, then saves the "screen" file as the WK4 file.
To open a BAK file, simply type *.BAK - which will then display all BAK files. If you CAN retrieve the BAK file, it will be because it was NOT backed up WITH the corruption, and therefore will NOT be as recent as the WK4 file. However, it probably will be more recent than your other WK4 backup files.
Here's hoping this will prove successful.
Regards, ...Dale Watson dwatson@bsi.gov.mb.ca
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question