[V4MD] pointer at the same table by binary_link

[Sims, John]

> -----Original Message-----
> From: valentina-beta-bounces at lists.macserve.net 
> [mailto:valentina-beta-bounces at lists.macserve.net] On Behalf 
> Of Ruslan Zasukhin
> Sent: Wednesday, September 14, 2005 5:13 PM
> To: valentina-beta at lists.macserve.net
> Subject: Re: [V4MD] pointer at the same table by binary_link
> 
> On 9/14/05 11:48 PM, "info at vallemediatime.com" 
> <info at vallemediatime.com>
> wrote:
> 
> >> So problem solved ?
> > Yes, now the problem is solved.
> > Thanks, your help it has been miraculous :-)
> > 
> > But I want ask you what do you think about the error message for 
> > linkRecords and unLinkRecords.
> > eg
> > If I add a link when it already exists, I don't get message... the 
> > final user see nothing;
> 
> Hmm, I am sure we throw error.
> 
> > but if I try to delete a link that non exist, I get a 
> message... and 
> > the final user see the a message.
> 
> Also correct.
> 
> > For me this is not good, I think that it's better use the 
> same solution:
> > or both methods have a message, or both methods have not message.
> > Do you agree?
> 
> Both must produce error
> 
> 
> --
> Best regards,
> 
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc

Ruslan,

I believe we had this dicussion before.  I believe you must consider the
intention in these situations.  When linking 2 records, the intention is
to have the 2 records linked together.  If they are already linked
together, then your intention is already met and Valentina should just
continue on.  If you unlink 2 records, the intention is to not have the
2 records linked together.  If the 2 records were never linked in the
first place, then your intention is already met and Valentina should
just continue on.

I believe that throwing errors in the situation where you are trying to
link 2 records that are already linked or trying to unlink 2 records
that were never linked in the first place is going to result in a lot of
error handler overhead that will be just there just to trap the error
and move on.  I thought this was the reason you created Link.LinkExists
for situation where developers wanted to check for the link before
proceding...

If myLink.LinkExists(a,b) Then
	msgBox("Link Exists")
Else
	myLink.LinkRecords(a,b)
End if

MUCH!!!! Faster resulting application than one that uses Error Handlers.

Sorry I am late to the discussion, I was out of town.

-My 2 cents

-John