GTRR error capture

[fabriceN]

OK, everybody knows that a Go To Related Records script step should always be checked in order to know if it was successful or not... but I couldn't expect this to become so tricky if GTRR is set up to show related records only, with a 'Match foundset' option.

This file illustrates unconsistancies of GTRR behavior and error code returned. More than a bug report, I think one should not ignore these results. I wonder how many bugs I ran into just because of that...

Hope this helps.

GTRRbugReport.fp7.zip

[fabriceN]

Wow ! I'm impressed that you all knew about that ! I realise I still have so much to learn...

[David Jondreau]

I brought up some of these GTRR issues a month or so ago. Your analysis is comprehensive and appreciated, but I pretty much don't use GTRR anymore because error trapping is too difficult.

[fabriceN]

Thank you. I had not found your post. Indeed, it's the same subject, except that I found some more incredible bugs for the same script step, that expose our solutions to high risk.

Now, I would love you to explain how you do without GTRR. Always with a find ?

Edited November 22, 2007 by Guest

[David Jondreau]

I wrote hastily. I'm trying to think of what I've done in the past month, and I can't think of many examples.

I guess it depends on whether I'm matching a single record or a found set. If it's a single record, I would test for related records first before each GTRR.

If I'm matching a found set, I'm not sure what I'd do.

I don't use Permissions to lock layouts, so that's not an issue.

In your tests did you look at whether your matching a single record or a found set? As I noted in the other thread, I've noticed some weirdness there, such as matching a found set that has matching records but not for the current record.

[fabriceN]

All these tests are ONLY in this case matching foundset with no record related to current record.

For some with records related to other records of current foundset (error 101), some no related record at all (401).

What I would do, now that I know all this would be, for every GTRR, and unless someone has a better idea :

- set a variable to target layout name

- check that this layout is among the layout names of destination file

- if yes, perform browsing action (GTRR, Go to layout) using the variable as a calculation by name

- trap error. 101 if "Match current record only", 401 if "Match foundset".

Edited November 22, 2007 by Guest