recovering damaged runtime files

[tomp]

The 'recover file' script step will not allow me to open/recover a damaged runtime data file. In fact, all runtime data files are 'grayed out' and can not be opened in the recover file script step.

What am I missing? Or am I (and my users) out of luck?

[CyborgSam]

The runtime file is exactly the same as an .fp7 file, it can be renamed with the usual .fp7 file extension to access it in the usual ways.

[tomp]

I find it interesting that in FM6 the file recover script worked on runtime files with extensions different than .fp5, but in 7 it doesn't work unless the extension is .fp7.

Is there a reason why in 7, a user for whom a runtime solution has been provided and who should have no need to understand how or why various extensions are used should have to go through a file rename in order to use a file recovery routine??

How does this work in FM8??

[T-Square]

I haven't tried to do what you're trying, but you might want to be sure that the permissions in the runtime are set correctly before you bind.

I had a runtime that I burned in which I had neglected to allow exporting of records; I had to re-open the file in Developer with my access rights in order to extract the data that the client should have had access to.

HTH,

David