Hi Brian,
The "test" database isn't working right. When I try to create new
record, I get a "121" error.
Charles
Brian Hancock wrote:
Hi Charles,
I have attached an STR which hows a
Keep as Total can force a related field to be created in a foreign
panel, when it otherwise wouldn't.
As a simple example the AutoCreate
field on a datalink doesn't always AutoCreate. It relies on something
being typed into the field with the DataLink but if you use a
calculated value for it, it doesn't AutoCreate.
In the Test.dat panel and just type
in your name and save the record, exit the panel and then look at the
Categ.dat and Categ2.dat panels. The second has
the category but the first doesn't..
If you create a second record in the test.dat panel, but instead of
accpeting the calculated category type something else in that field,
and you will create the related record. Both Category fields are the
same, but the second one uses the Keep a Total. Normally I would hide
the links and the fields.
Ralph Alvy's book discusses many of
the uses of the Keep A Total field. It really is a great feature of
DP, a feature which is totally missing from products like Microsoft
Access, and which requires good SQL programming skills to implement in
SQL type databases like SQL server, MySQL, Oracle etc.
Regards
Brian
-----
Original Message -----
Sent:
Monday, February 18, 2008 2:06 PM
Subject:
Re: [Dataperf] Mailing list management
Brian,
Would you give me an example of the use of forcing DP to create related
records when it might otherwise not, please.
And thanks for your great suggestions. You dazzle me!
Charles
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 -----
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 -----
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
|