Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

WwWXxX, udp high ports, d-link extract firmware dsl-2750u, wwwwxxxxx.2G, yxxxcom, WWWXXX, ftp://192.168.100.100, wwwxxx 100, www.xxxcon, wwwxxx

Links

XODOX
Impressum

#1: Recover issue

Posted on 2008-04-23 19:24:49 by Bill Jaynes

I am using FM5 to recover a runtime file that is also FM 5 on an XP
machine. In the past, the recover command has worked flawlessly 99% of
the time. Today however, with this particular file, I choose Recover,
agree to the new name in the browser panel and click Save. Nothing at
all happens; not the usual panel with progress and rebuilding
information etc. Is this a sign the file is unrecoverable? I expected
it to at least try and report failure but exactly nothing happens
after clicking Save.
Thanks,
Bill

Report this message

#2: Re: Recover issue

Posted on 2008-04-23 21:55:57 by E W P Appeldoorn

<bjaynes@montanaport.net> schreef in bericht
news:64bda809-a26b-4ca2-a372-749cf30f8bc6@34g2000hsf.googleg roups.com...
>I am using FM5 to recover a runtime file that is also FM 5 on an XP
> machine. In the past, the recover command has worked flawlessly 99% of
> the time. Today however, with this particular file, I choose Recover,
> agree to the new name in the browser panel and click Save. Nothing at
> all happens; not the usual panel with progress and rebuilding
> information etc. Is this a sign the file is unrecoverable? I expected
> it to at least try and report failure but exactly nothing happens
> after clicking Save.
> Thanks,
> Bill

Generaly the recover command is badly named. VERY badly. It is only meant to
get access to a file long enough to export the contents to an other,
undamaged, file. Recovering does NOT heal it, only makes it work again. Any
(or even many) errors may still lurking in the file and will probably appear
again at some stage. Relying on recovering is therefore bad practice,
specialy when you are going to work with the file again. Worse still when a
new error appears and you do a renewed recover. You should always have a
fresh clone as a backup. AND always have a good backup system in place.

As for this file, make sure it is not write protected. Otherwise see if you
know someone with FMP9, this has a more rigoroius error checking and
recovering. Then you might export the contents as tab or csv. If this
doesn't help go back to the last working backup, You will have to rebuild
your solution, because the error will probably already is in the file, but
at least you could rescue some of your data.

Keep well, Ursus

Report this message

#3: Re: Recover issue

Posted on 2008-04-23 23:50:40 by Bill Jaynes

Hi Ursus,
Well, I was just wanting to recover it pull data out only, not to
reuse it. It's not write protected either. It was just curious that FM
wouldn't even start a recovery panel, just blinked out. It's someone
else's file; he didn't do any backups and is accepting of having to
start with another solution now. Thanks for your input.
Bill

Report this message