Groups | Search | Server Info | Login | Register

Groups > comp.databases.filemaker > #301

Re: GTRR in scripts

Show all headers | View raw

David Jondreau <david@wingforward.net> wrote:

> It's unclear what you're trying to accomplish, but two things come to
> mind:

GTRR for all records of my present found set. Find out whether there are
related records at all. The found set may be 4'000 records, of which
1'500 have child records.

> 
> 1) Error 401 is a better test than 101. You get 101 when matching the
> found set and the record that's currently active has no related
> record. 401 pops up when there's no related records at all.

Great. I'll test for 401.

> 2) Are you using this db locally or over a network? I find GTRR
> matching the found set to be extremely slow over a network. I've
> tested it and found it faster to loops through the found set, setting
> a global field to the related keys and GTRR on a new relationship
> based on that global field, matching the current record only.

Good to know when speed issues come up. The db is local, though.
-- 
http://clk.ch

Back to comp.databases.filemaker | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

GTRR in scripts clk@tele2.ch (Christoph Kaufmann) - 2011-07-03 07:44 +0200
  Re: GTRR in scripts David Jondreau <david@wingforward.net> - 2011-07-03 10:31 -0700
    Re: GTRR in scripts David Jondreau <david@wingforward.net> - 2011-07-03 19:35 -0700
    Re: GTRR in scripts clk@tele2.ch (Christoph Kaufmann) - 2011-07-04 06:04 +0200
  Re: GTRR in scripts cortical <cb@corticaldata.com.au> - 2011-07-04 12:02 +0930
  Re: GTRR in scripts clk@tele2.ch (Christoph Kaufmann) - 2011-07-04 06:09 +0200

csiph-web