Go to related record randomly not working in IWP

[tminogue]

Help!

I am having problems with a Filemaker 9 IWP dbase. I have a table called "Destinations" with a portal listing all records in the destination table. The user enters their password into a global field called "zpassword." This table is related to a "Comments" table by "Destination_ID" to "xDestination_ID" and "zpassword" to "xpassword". When a user clicks on a record in the portal it either creates a new related record for them in the "Comments" table (and takes them to that layout) or takes them to an existing related record. This has been working beautifully (~3600 records created without any problems) except for 5 specific times when a user clicked on a destination and rather then creating a new record in the comments table, they were directed to a random existing record with either or both wrong Destination_ID and xpassword.

The script is as follows:

If [Comments::DummyField="Yes"]

Go to Related Record [show only related records; From table"Comments"; Using layout:"Comments" (Comments)]

Else

Insert Text[select; Comments::DummyField;"Yes"]

Go to Field [Comments::Yes_no]

Go to Related Record [show only related records; From table"Comments"; Using layout:"Comments" (Comments)]

End If

Any ideas or suggestions?

Thanks.

[RJS-IT]

Here are my thoughts, I hope they help:

a) why is a password being entered to view a record? Surely it would be better for users to Log in with an account, then your opening script (on relogin script) can set a $$ or global field to restrict what records are visible.

: when starting to use IWP i had simlar random problems with wrong records i did the following and havent had a problem since (possibly by more luck than knowledge);

- 1: dont use goto related record, instead use $ID variables to mark the portal row (the relating record reference) selected at the start of any script and do it in full - goto layout, enter find mode, set field with the $ID, perform find...

- 2: dont use insert text - always set field. And more importantly, use it when the target layout and record are locked in.

Anyhow Good Luck