[AccessD] Design Question

On 2/6/07, Jim Lawrence <accessd at shaw.ca> wrote:

> The above would be correct (I will assume that each record in each of the
> tables has a field name ID) and if you add a table named 'CONNECTION' with

Correct assumption. I've bashed that into his head :)

> only two fields, additional to its own ID field.
>
> One field could be named OwnerID and the other field OwnedID. The records in
> this table would be created when a relationship was established in code, one
> for each relationship. The beauty of using this type of table is that
> one-to-one, one to many, backwards or forwards and even reciprocal
> relationships (the table could call it's self) could used...

How would you know which table the OwnerID and OwnedID belongs to?

> The only particular about this type of table is that you as the programmer
> would most likely have to maintain it with your code.... sorry not bound.
> This system works great and I have used it to resolve many similar issues.

In this case, I doubt it's gonna happen. He's not a programmer. Just a
manager :)

-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a well
preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"