Scott wrote:
>Sounds like a recipe for spaghetti to me. What happens when the
>source field changes, do all fields that point to it have to be
>live-updated with it? And what if you change the field, does the
>"sourceField" get updated? What happens with fields with sharedText
>set to false, do you have to specify the card? And the biggest
>question: What would this be useful for?
I don't think this is a recipe for spaghetti, Scott, just an extension of
the sharedText property notion. The idea is similar to setting up a
relational field in FileMaker as in "::Address1" with the ability to link
the text contents of one field by reference to changes made in the text
contents of another field (so that changes made in the "sourceField" are
live-updated in their "aliases" automatically). Changes would be one-way
only so any "alias" field would effectively have its lockText and
sharedText set to true.
set the icon of btn 1 to <image id>
set the sourceText of fld 1 to <fld id>
The reason for this? Setting up relational fields. Phil suggested using
htmlText, and both Dave and Mary suggested using a preOpenCard handler to
re-build field contents on-the-fly. However, since each record in the
system has multiple and independent address sections comprising over 30
fields in total and all have to searchable, I have had to implement
relationship tables (triggered on closeField in each "source" field) for
live-updating of all related "alias" fields on all related cards. It now
works very well, but was truly horrible to do and would have been so easy
with a sourceField property.
/H
Hugh Senior
The Flexible Learning Company
Consultant Programming & Software Solutions
Fax/Voice: +44 (0)1483.27 87 27
Email: [EMAIL PROTECTED]
Web: www.flexibleLearning.com
