One Pointer Field Fits All

[Ruslan Zasukhin]

On 5/30/05 2:16 AM, "Chuck Pelto" <cbpelto at pcisys.net> wrote:

Hi Chuck,

> Yeah...
> 
> ...that's sort of what I was afraid of; a separate pointer field for
> each of the tables that would like access to the Notes table. This,
> in spite of the idea of two fields, one to identify the table and one
> to identify the record inside of the table.
> 
> Think you might be able to do that in a future edition?

But this is correct solution IMHO from all points of view.

It seems to me you think about contrast way:
    - putting into table Notes pair of field {TableId, RecID}

Right ?

Well, Valentina 2.0 introduce new field "OID" for each table.
Values of this field is exactly what you want.
It is {TableId, RecID}.

So you can use OID values to store them into Notes.ULLong field.

Having this you will need self extract from Notes.ULLong field value the
part of pointed TableID and its RecID.

Also you will meet problem that REALbasic do not support ULLONG.

Also you can at last of end to make own 2 fields and keep there
    TableID + RecID

 
> Regards,
> 
> Chuck
> 
> 
> On May 29, 2005, at 8:48 AM, Ruslan Zasukhin wrote:
> 
>> On 5/29/05 4:22 PM, "Chuck Pelto" <cbpelto at pcisys.net> wrote:
>> 
>> 
>>> Another question.
>>> 
>>> I have a table I refer to as Notes. I would like that table to be
>>> used to hold ALL notes in a given RB project. This, no matter, what
>>> other table those notes might belong to.
>>> 
>>> Is there a technique to have one field act as the differentiator as
>>> to which table the notes will appear in? Something along the lines of
>>> a field in Notes to identify the other table a given note belongs to
>>> and the pointer field to identify the record in that other table the
>>> note is associated with?
>>> 
>>> This was easily accomplished in FileMaker. Just set up the link in
>>> the table that the note was supposed to be related too in Notes.
>>> 
>> 
>> So this is easy?
>> I.e. If you have 10 tables around, you need make 10 links?
>> 
>> 
>>> How
>>> can that be done in V4RB? I'd like to avoid having to put a separate
>>> pointer field in Notes for every other table that would require an
>>> ability to have Notes associated with it.
>>> 
>> 
>> Pointer field must be in each of this 10 tables,
>> I.e. You get the same 10 links

-- 
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]