This Q is more nuts and bolts...

If you've got layouts using a Table Occurrence in file A and another
in file B that both refer to the same base table, is there any way to
transfer the found set in A to B.

Within a single file the GTRR script step can be used, but I can't
seem to see how to set it up to work with an external layout/file.

This is coming up in a multifile solution, where some actions must
executed in a different file due to permissions/security restrictions.
(Only scripts in the file actually containing the table can exceed the
logged in users priviledges for that table.)

-best regards,
Dave

On 29 Apr 2007 16:30:47 -0700, d-42 <db.porsche (AT) gmail (DOT) com> wrote:

How about exporting the found set from A into a separate, but
duplicate table in B having a related key to the original table? Then
you could run your script on the found set in B, import the changes
into A and wipe the found set from B when finished.

--
FW

On Apr 29, 11:05 pm, FastWolf <wolfsof... (AT) gmail (DOT) com> wrote:
Yes, that will certainly work.

Even better is to export the PKEYs to a one field empty table, with a
TO in both files, and a relationship defined in the 2nd file on that
key back to the main base table, and then GTRR matching all records in
the found set. That reduces the problem to a single export, and
eliminates having to import back and forth.

Another way is have a marker field and replace it with a tag in the
found set. Flip to the other file, and perform a search on the tag.

All the above work. (Although all 3 are made more complex if they are
to be multi-user safe).

But I was really hoping there was some way of mangling the GTRR script
step a little more cleverly than I had been.

-cheers,
Dave