Capturing "File is damaged..."

[Howard Schlossberg]

Although it is defined as error code 805, there is no way to block the
message dialog from popping up, even when the Set Error Capture step is
set properly. You can trap for errors in your script immediately after
the Open[] step where this error is generated. The user will still get
the default dialog, but at least your script will know it by checking
for error 805.

Bill Jaynes wrote:

> Hello,
> I would like to build an opening script that suppresses Filemaker's
> "File is damaged and cannot be opened. Use the Recover command..." and
> allows me to display a custom message. I imagine the syntax is something
> like..
> If (Status current error = ........) show message.
> Not sure about how to word that.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg (818) 883-2846
FM Pro Solutions Los Angeles, California
Associate Member, FileMaker Solutions Alliance

[Bill Jaynes]

I have tried a couple of things:

Set Error Capture ON
Open (damaged file)
If Status Current Error = 805
Show Message
End If

This brings up the dialog as you say. I hoped to be able to cancel out of it
and have my message show. If I cancel out of the Recover dialog the script
ends without the message. If, however, I specify If not(Status (current
error)) = 805, my dialog shows. I checked how the Status function works; it
needs a number result but wants only to be boolean. I think I'm close; any
ideas?
All the best,
Bill


"Howard Schlossberg" <howard@antispahm.fmprosolutions.com> wrote in message
news:vgtu2r8k35ja46@corp.supernews.com...

> Although it is defined as error code 805, there is no way to block the
> message dialog from popping up, even when the Set Error Capture step is
> set properly. You can trap for errors in your script immediately after
> the Open[] step where this error is generated. The user will still get
> the default dialog, but at least your script will know it by checking
> for error 805.
>