why need uniq key on master in relation?

  • Thread starter Thread starter Mtcc
  • Start date Start date
M

Mtcc

why need uniq key on master in relation?

(it seem like stupid thing. again and again microsoft going revese)

take look in access, when you need to write Master-detail, make
subform, and link it parant-child, and not need any key on master!

take look in VB6 with DataEnvironment, make it easy without any uniq in
master.

why is need? who care, if on master have many record, that linked to same
record?

have sombody to explain as why microsoft make this?
 
Hi Mtcc:

I'm not sure I follow you here. In Vb6 you don't have to explicitly specify
an object's type and that makes things a lot easier. Would you call that an
improvement? I can't answer why they forced the issue with keys but
considering that you operate in a disconnected mode and that you have a ton
of pwer and flexibility, it's not surprising and certianly not unwanted.
 
Many reasons - for instance, how would you handle cascading keys if more
then one parent? You are looking at it for one perspective only, i.e. going
from parent to children, look at it the other way, from child to parent and
you will see that there are a number of issues.

Maybe you can achieve what you want by not using relations at all and
instead use the select or find methods on the datatable to get the children
you want.

Cheers,

Laurie Paulin
Perth, Western Australia
 
Back
Top