ParadoxField?

Maybe you could try explaining what you want to do without the example - be
specific even.
wrote in message

> Hi,
> I am trying to create a Database which should have fields
> pointing to a Paradox field. e.g:
>
> Table1 {
> int value;
> int value2;
> char Name;
> Table1 Person; <----- Is that possible, and how it's done?
> }
>
>
> regards
> M.
 >> Stay informed about: ParadoxField? 

Hi,
I'd like to do a Table containing my Family-Relationship( Record no1:
Me, Record No2: My Mother,...) I need a field in the Record which
contains the pointer to the Record containing the data of that
specific person.

e.g.: Table Person
RecordSet:
Field1 Name;
Field2 Birthday;
Field3 Adress;
Field4 Mother; <--------- other Record in the same table;
Field5 Father; <---------- " " " ;

I am sorry for that last example. I'm into C-Programming too.
Hope that helps.
M.

On Tue, 22 Apr 2008 11:19:32 -0400, "Jim Giner"
wrote:

>Maybe you could try explaining what you want to do without the example - be
>specific even.
> wrote in message
>
>> Hi,
>> I am trying to create a Database which should have fields
>> pointing to a Paradox field. e.g:
>>
>> Table1 {
>> int value;
>> int value2;
>> char Name;
>> Table1 Person; <----- Is that possible, and how it's done?
>> }
>>
>>
>> regards
>> M.
>
 >> Stay informed about: ParadoxField? 

There was a long discussion on just this sort of structure for
normalizing a set of relationships for people (and another for cows
IIRC) in the newsgroups. You may want to search for it (search on words
like Mother & Father (not child as that will get you a ton of non
relevant stuff) and maybe cows (in case I am remembering correctly) and
you should find the threads.

You may also want to read my Normalization primer which you can find on
our paradox resources page (link in my signature). It will help you with
things like why you should break addresses into a separate table and a
bunch of fields and then link people to addresses (some likely live
together, others will move over time, etc.) and break Name into parts,
pull out the relationships to a separate relationship table, etc.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

MichaelR RemoveThis @niemand.org wrote:
> Hi,
> I'd like to do a Table containing my Family-Relationship( Record no1:
> Me, Record No2: My Mother,...) I need a field in the Record which
> contains the pointer to the Record containing the data of that
> specific person.
>
> e.g.: Table Person
> RecordSet:
> Field1 Name;
> Field2 Birthday;
> Field3 Adress;
> Field4 Mother; <--------- other Record in the same table;
> Field5 Father; <---------- " " " ;
>
> I am sorry for that last example. I'm into C-Programming too.
> Hope that helps.
> M.
>
> On Tue, 22 Apr 2008 11:19:32 -0400, "Jim Giner"
> wrote:
>
>> Maybe you could try explaining what you want to do without the example - be
>> specific even.
>> wrote in message
>>
>>> Hi,
>>> I am trying to create a Database which should have fields
>>> pointing to a Paradox field. e.g:
>>>
>>> Table1 {
>>> int value;
>>> int value2;
>>> char Name;
>>> Table1 Person; <----- Is that possible, and how it's done?
>>> }
>>>
>>>
>>> regards
>>> M.
>
 >> Stay informed about: ParadoxField? 

Ah! recursion. If it's only to one level, then it's easy.

Persons
Field1 PersonID (Meaningless Identifier)
Field2 Name
Field3 Birthday
Field4 Address
Primary Key = PersonID

Relationships
Field1 RecordID (Meaningless Identifier)
Field1 PersonID - points to Persons record of this person
Field2 RelativeType - 1 = Father; 2 = Mother, 3 = Brother, 4 = Sister
Field2 RelativeID - points to PersonID of relative
Primary Key = RecordID
Secondary Index on PersonID + RelativeType + RelativeID (Unique)

Then you can look at a person and find all their relatives. For father,
look for RelativeType = 1, Mother = 2, all brothers = 3, all sisters = 4.

HTH

MichaelR.TakeThisOut@niemand.org wrote:
> Hi,
> I'd like to do a Table containing my Family-Relationship( Record no1:
> Me, Record No2: My Mother,...) I need a field in the Record which
> contains the pointer to the Record containing the data of that
> specific person.
>
> e.g.: Table Person
> RecordSet:
> Field1 Name;
> Field2 Birthday;
> Field3 Adress;
> Field4 Mother; <--------- other Record in the same table;
> Field5 Father; <---------- " " " ;
>

--
Tom Krieg

---------------
http://www.krieg.com.au
http://www.fam.krieg.com.au
Please use the contact page to contact me via email
 >> Stay informed about: ParadoxField? 

In the Relationships table, also create another secondary index on
RelativeID, then you can do a reverse search. This gets a little more
complicated.

Add an extra 2 options to RelativeType -5 = Son, 6=Daughter

Tom Krieg wrote:
> Ah! recursion. If it's only to one level, then it's easy.
>
> Persons
> Field1 PersonID (Meaningless Identifier)
> Field2 Name
> Field3 Birthday
> Field4 Address
> Primary Key = PersonID
>
> Relationships
> Field1 RecordID (Meaningless Identifier)
> Field1 PersonID - points to Persons record of this person
> Field2 RelativeType - 1 = Father; 2 = Mother, 3 = Brother, 4 = Sister
> Field2 RelativeID - points to PersonID of relative
> Primary Key = RecordID
> Secondary Index on PersonID + RelativeType + RelativeID (Unique)
>

--
Tom Krieg

---------------
http://www.krieg.com.au
Please use the contact page to contact me via email
 >> Stay informed about: ParadoxField? 

Hi,
yes it's recursion. But I suppose more than one level. I would take it
as fas as plausible data takes me.
In the Table Relationships.Field1 (PersonsID) which field type do you
take? That is my main problem.


M.

On Wed, 23 Apr 2008 19:12:35 +1000, Tom Krieg <"Please use the website
contact form"> wrote:

>In the Relationships table, also create another secondary index on
>RelativeID, then you can do a reverse search. This gets a little more
>complicated.
>
>Add an extra 2 options to RelativeType -5 = Son, 6=Daughter
>
>Tom Krieg wrote:
>> Ah! recursion. If it's only to one level, then it's easy.
>>
>> Persons
>> Field1 PersonID (Meaningless Identifier)
>> Field2 Name
>> Field3 Birthday
>> Field4 Address
>> Primary Key = PersonID
>>
>> Relationships
>> Field1 RecordID (Meaningless Identifier)
>> Field1 PersonID - points to Persons record of this person
>> Field2 RelativeType - 1 = Father; 2 = Mother, 3 = Brother, 4 = Sister
>> Field2 RelativeID - points to PersonID of relative
>> Primary Key = RecordID
>> Secondary Index on PersonID + RelativeType + RelativeID (Unique)
>>
 >> Stay informed about: ParadoxField? 

Sorry, that should be

Relationships
Field1 RecordID (Meaningless Identifier)
Field2 PersonID - points to Persons record of this person
Field3 RelativeType - 1 = Father; 2 = Mother, 3 = Brother, 4 = Sister
Field4 RelativeID - points to PersonID of relative
Primary Key = RecordID
Secondary Index on PersonID + RelativeType + RelativeID (Unique)

You should also include son/daughter in the relative type.

In Paradox, I would make PersonID and RecordID fields meaningless long
Integers, in a MS SQL database a GUID would be suitable. The RecordID
field identifies a unique relationship of one person to one other
person. You wouldn't necessarily use this in your logic but Paradox
requires a unique primary key to have secondary indexes. You could, of
course, have a primary key of PersonID + Relative Type + RelativeID as a
compound key.

It's the PersonID key in the Persons table that has a relationship to
the PersonsID field in the Relationships table (1 -->>M) via the
secondary index (this links all immediate relatives 1 generation up, one
down and one sideways), and the RelativeID field in the Relationships
table relates back (1 --> 1) to the PersonID of the relative via the key
of the Persons table.

Through recursion, you can step through the database up, sideways or
down for as many levels as you want.

MichaelR.DeleteThis@niemand.org wrote:
> Hi,
> yes it's recursion. But I suppose more than one level. I would take it
> as fas as plausible data takes me.
> In the Table Relationships.Field1 (PersonsID) which field type do you
> take? That is my main problem.
>
>



--
Tom Krieg

---------------
http://www.krieg.com.au
Please use the contact page to contact me via email
 >> Stay informed about: ParadoxField?