Breaking Relationships

[Matt Revenaugh]

Does anyone know of a way to "lock" relationships?

If a db is related to second db on the network, and the network is down or
unavailable, the user is prompted to find the db. More than once a user has
picked the first file he sees which is always wrong. Then it breaks the
relationship and the entire chain of links. What a pain!

I can't error trap around the the problem. Any suggestions?

All these FileMaker Pros, I can't imagine I'm the only one who has run into
this problem.

Matt Revenaugh

[Glenn Schwandt]

Don't allow FileMaker to search for the required database itself. Before
the user is prompted to find the database (whatever process is causing that
in your database), run a script like the following:

Set Error Capture [on]
Perform Script [Sub-scripts, YourNetworkDB]
- select a script that has one step: Toggle Window [minimize]
If [Status (CurrentError) <> 0]
Show Message ["YourNetworkDB is not available"]
Halt Script
End If

You could also substitute the Open script step for the Perform Script above,
which will cause the startup script (if any) to run (assuming the database
is not already open).

"Matt Revenaugh" <mrevenaugh@bak.rr.com> wrote in message
news:BB42D9F8.19CC8%mrevenaugh@bak.rr.com...

> Does anyone know of a way to "lock" relationships?
>
> If a db is related to second db on the network, and the network is down or
> unavailable, the user is prompted to find the db. More than once a user

has

> picked the first file he sees which is always wrong. Then it breaks the
> relationship and the entire chain of links. What a pain!
>
> I can't error trap around the the problem. Any suggestions?
>
> All these FileMaker Pros, I can't imagine I'm the only one who has run

into

> this problem.
>
> Matt Revenaugh
>

[Glenn Schwandt]

Then run the script before you allow the portal to be displayed.

"Matt Revenaugh" <mrevenaugh@bak.rr.com> wrote in message
news:BB42E5C7.1A165%mrevenaugh@bak.rr.com...

> I display a portal with the related records. So FM automatically opens the
> related file.
>
> Matt Revenaugh
>
> --------
>
> On 7/22/03 12:44 PM, in article [email]vhr515rfnkve61@corp.supernews.com[/email], "Glenn
> Schwandt" <schwandtgat@aoldot.com> wrote:
>

> > Don't allow FileMaker to search for the required database itself.

Before

> > the user is prompted to find the database (whatever process is causing

that

> > in your database), run a script like the following:
> >
> > Set Error Capture [on]
> > Perform Script [Sub-scripts, YourNetworkDB]
> > - select a script that has one step: Toggle Window [minimize]
> > If [Status (CurrentError) <> 0]
> > Show Message ["YourNetworkDB is not available"]
> > Halt Script
> > End If
> >
> > You could also substitute the Open script step for the Perform Script

above,

> > which will cause the startup script (if any) to run (assuming the

database

> > is not already open).
> >

>