Good thoughts, Carl. This explanation of 'order of logical operations' (?)
for FMPro is helpful for me.
I'd like to add for interested folks that being able to mark a certain found
set (for further narrowing of the query later) would be a handy skill. One
could ADD a field to the particular file in question (names, payments, etc.)
for just this purpose.
There is a field (FoundSetKey) in NAMES_.102 already used by FMPro for this
purpose when one uses the TRANSFER TO NAMES button on any of a number of
layouts (in Payments, Notes, etc.). If one uses this field wisely, it could
be handy for marking NAME records -- the only hassle would be if you tried
to use one of the TRANSFER TO NAMES buttons in the middle of whatever you
were doing. As I recall, when you TRANSFER TO NAMES, this field is updated
with some kind of current date/time info for the found set in question, so
careful use of the field for other purposes might not cause permanent
pollution of the data ... in other words, whenever you use a TRANSFER TO
NAMES button, this field is updated with current date & time, and then the
script goes over to the NAMES_.102 file and queries the file for records
with that date & time in that field. The next time, a different date/time
is used for that found set, so maybe one could use it in the meantime?
Maybe it'd be _cleaner_ to just add a field, though.
-- Eric Johnson
Colorado Environmental Coalition
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
