ObjectPtr - What's the best way to create a new ObjectPtr link for two existing tables. Both have existing data.

[Ruslan Zasukhin]

On 9/6/07 11:43 PM, "Barry G. Sumpter" <BarrySum at BigPond.Net.AU> wrote:

Hi Barry,

> Hi all,
> 
> For my sample scenario:
> 
> I have a SoldInPostCode table with 100,000 records.
> (I've sold 100,000 widgets.)
> Each record has just a single field of a Postcode in it.
> It is numeric.
> And the max value is 99999.
> The PostCode is NOT unique.


-------------------
> I have a PostCodeWithState table with all the PostCodes with their States.
> (I want to know how many widgets were sold in each state)
> 99999 postcodes within 52 states.

> There are two fields.

> Each record has a single field of a Postcode in it.
> It is numeric.
> And the max value is 99999.
> 
> Each record also has a single field of a State in it.
> Lets say for now it is a string.
> 2 characters long.
> And contains the 52 State abbreviations.  TX, OK, CA.
> 
> So the Left table has 100,000 Records.
> I want to like to the right table that has 99,999 records.
        ^^^^^^^^ to link ?

So you have tables 
    SoldInPostCode and PostCodeWithState

Linked as 
    One to Many

With help of RDB-link, i.e. Link By Value.


> For this scenario I want an ObjectPtr
> So I've already created an ObjectPtr field: SoldPC_PCState.

First Note. 

I recommend to name an ObjectPtr field as

    PersonPtr

So for your case e.g.
    SoldInPostCodePtr






-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]