Hi Marcos,Just for a matter of curiosity I wanted to see how robust recursive linking could be. So I created a single panel Family Tree database. It is very trivial in that Names can't be duplicated, but there are many recursive links, to enable all sort of calculations and filtering. It does some interesting things, including some very curious things. I have attached the STR.
Because of Keep A Totals thru links, a Blank record is created. You cannot delete that record. As soon as you Delete it, it comes back. You will upsets count if you try to reuse the record, by adding a name into it. In fact another blank record will be created as well.
Normally when I need to change a panel's definition, I will 1. Export data with Shift-F7 Built In Short Reports2. Remove All records in File with Alt-F5 (generally with Delete records with Non totalling)
3. Make changes to definition 4. Import data Ctrl-F5 (No Totalling)If you have accidentally reused the Blank record, and want to get the count correct you need to zero all the count of children fields (I included a Shift F7 report to do that), export the data, remove the records WITHOUT totalling, and reimport them WITH totalling. However when you Import the data, you will find that the Import reports a number of duplicate records, and misreports the number of records imported. It actually does import all the records correctly, and the number of records will be equal to the number is said it imported plus the duplicates it skipped...
So, even though I said that you do not need to do anything special when using recursive links, it depends on what you do. If you use Keep a Totals through the recursive links, although you can do some really nifty things, you might find odd consequences.
Regards Brian----- Original Message ----- From: "Brian Hancock" <[EMAIL PROTECTED]>
To: "Dataperfect Users Discussion Group" <[email protected]> Sent: Friday, January 19, 2007 12:30 AM Subject: Re: [Dataperf] Recursive link
Hi Marcos,The recursive link doesn't require anything special. If the lookup is working, then it should be fine.Ralph's book shows creative uses the recursive link, but the type of recursive link you mentioned is frequently used just the way you described.Regards Brian----- Original Message ----- From: "Marcos Favero Florence de Barros" <[EMAIL PROTECTED]>To: "DataPerfect Users Discussion Group" <[email protected]> Sent: Thursday, January 18, 2007 11:45 AM Subject: [Dataperf] Recursive linkDear DP discussion group colleagues, In a database I implemented (as voluntary work) for a public Health Center, there is a "Name" field, and a "Mother's Name" field, both in the Client panel. Many mothers are themselves clients of the Health Center, and have their own records. So, to help fill out the field "Mother's Name" when the record of a child is being created, I made a Data Link going from the "Mother's Name" field to the "Name" field, which is in the same panel. Ralph Alvy calls this a Recursive Link, but his book concentrates on special uses of the recursive link, whereas all I want is a pick list to help fill out the "Mother's Name" field. Apparently it works, but I wonder whether there are any potential problems, or special precautions to be taken. Thanks, Marcos Florence ---------------------------------------- Marcos Favero Florence de Barros Campinas, Brazil [EMAIL PROTECTED] _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
FAMILY.STR
Description: Binary data
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
