Hi Charles,
I am a little lost, would you like to send the STR to my personal email [EMAIL
PROTECTED] so I can get my head around what you are doing.
Regards
Brian
----- Original Message -----
From: Charles G. Wolf
To: Dataperfect Users Discussion Group
Sent: Thursday, May 01, 2008 2:56 PM
Subject: Re: [Dataperf] Mailing list management
Hey Brian,
I'm working on this Address Management panel, and with an idea from Rich
Bragonje, I now have a pick list from which to choose a reason for a
return/change. Some reasons for removal (customer calls or I decide to remove
name) demand an immediate removal from mailings, while others (undeliverable
mail) must wait for a second occurrence before. While an address change
happens immediately and the customer stays on mailing lists.
being removed.
I can't figure an elegant way to do this. And, I'm having trouble getting my
mind around Keep a Total. I know KAT should be used for the
second-occurrance-needed situation. And that there must be a field back on the
main Name panel. But can I use that same field for the situation that demands
an immediate removal, or do I need another field. How to implement the KAT
also flummoxes me.
It's been 10 years since I've done serious design work on this db, and I'm
rusty. I would appreciate any pointers.
Thanks.
Charlie
Brian Hancock wrote:
You could place a second field on the parent panel and initialise it to say
"X" on create, and set a formula to have it change to "" when the kept total
field reaches 2. You can then use an Exception List onthe index so that if that
field is empty then the record is not visible. (Remember not to keep an
exception list on all indexes, otherwise the record will be hidden from
everything until you remove the exception list... even export and imports will
might cause you to create orphaned child records...
The Keep a total is one of my favourite things with DP. Apart from keeping
total and setting flag you can use it for such things as forcing DP to create
related records when it might otherwise not, and you can use it for conditional
incrementing when you do not want to use recursive numbering . (For instance
line numbers in invoice details, and then use formula on Create to use the kept
total + 1 as the next line number, etc... btw recursive number is better in
that case anyway., just harder to implement.)
Regards
Brian
----- Original Message -----
From: Charles G. Wolf
To: Dataperfect Users Discussion Group
Sent: Monday, February 18, 2008 10:36 AM
Subject: Re: [Dataperf] Mailing list management
Hi Brian,
That is exactly what I'll do. I forgot about Keep a Total because I've
never used it! Your suggestion is easy to implement.
Any idea on how to mark hte date when the record reached two returns and
thus, is off the list?
Charles
P.S. I solved the previous problem by creating an "Outside List" child
panel, with an indicator in the parent panel whether there are records in the
child panel. Then with each mailing that's been specified from the outside
source, I import their list into the Outside List panel (my unique ID is still
with their record), run the report that creates the mailing record, then delete
the records from the Outside List panel. Works like a dream.
Brian Hancock wrote:
Hi Charles,
I guess you are storing returns in some child panel? If so, using Keep
a Total, can be used to count the number of records matching a criteria (ie
formula on a flag field indicating 1 or 0 . The kept total is on the parent
panel, and if you do not want to chow it or take up valuable real estate then
use a G9::H field. Refer to that field to check that it is less than 2 when
send ing mailings.
Regards
Brian
----- Original Message -----
From: Charles G. Wolf
To: DataPerfect Users Discussion Group
Sent: Monday, February 18, 2008 10:01 AM
Subject: [Dataperf] Mailing list management
Hi Everybody,
Does anybody here have experience with mailing list management?
Specifically, I want to track returns, so after two returns, the name is
flagged off the mailing list. I also want the date the name was flagged off
recorded.
Any suggestions?
Thanks.
Charlie Wolf
----------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
--------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
----------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
