Using the Recover command

[Lawlerdev]

I have just updated to FM Dev 5.5 and I find that when I use the recover command through a script in the unbound solution it renames the files as xx Recovered.FP5.

When I bind the solution it renames the file as xx Old.FP5.

This really screws up a utilities solution I have developed.

Has anyone any solutions??

[Steven H. Blackwell]

Why are you running the Recover command on these files? You should not use recovered files. THe purpose of Recovery is to get the data out of the file so they can be placed into a clean clone.

Old Advance Man

[IdealData]

I've read many posts on this subject and I'm not convinced that using a recovered file is wrong.

In my development system I use a lot of GLOBAL fields, often to store "fixed" data, especially graphics - unfortunately when you make a clone you lose the content of your GLOBALS. Whilst it is true that I could initialise the GLOBALS in each file in a start up script for text and numbers and dates, I can't do this for containers.

The issue of re-importing the data is one of volume. I've seen a number of postings with people claiming 500,000+ records in some files. In a large networked system you can't afford the down-time imposed by the re-import issue. My system alone would probably take most of a working day, and I've only 170Mb of active data.

Back to backup is safest !

If you have the same as myself then your clone must be an empty file, created by deleting all the records.

[Steven H. Blackwell]

Backups are essential. But many people don't ever bother to see if their backups actually work. And if you backup a corrupted file, then the bckup is corrupt as well.

If a file needs to be recovered, then per se it has experienced some sort of corruption. The purpose is to get the data out of it. FMP will sacrifice anything in a file's structure to preserve data.

Old Advance Man

[Lawlerdev]

I understand that one should never use a recovered file. However the way my application has been designed is to recover the damaged file in the application folder, import the data to a fresh clone in the utilities folder and then replace the original file in the application folder.

All of this works fine when running under full 5.5 but the scripts fail when the name of the recovered file is no longer xx recovered.FP5 but xx Old.FP5.