6.5 Bug with !@IsMember <> @IsNotMember?

Hello,

I just changed to 6.5 domino and 6.5. designer, when hiding Buttons in the Outline i used to

do this like this:

(setupuser is a view maintained by the admin)

(X) Hide when formular true

!@IsMember(@DbColumn(“”: “NoCache” ; “”:“” ; “setupuser” ; 9); @Name([CN];@UserName))

This one doesn´t work anymore, i changed the Formula like this:

@IsNotMember(@DbColumn(“”: “NoCache” ; “”:“” ; “setupuser” ; 9); @Name([CN];@UserName))

and it worked ?!?!?

So !@IsMember is not the same like @IsNotMember.

Whats your expirence ?

Subject: 6.5 Bug with !@IsMember <> @IsNotMember ?

!@IsMember was never the same as @IsNotMember.@IsMember means “is a subset of”. The order of the parameters matters.

So !@IsMember means “is not a subset of”. The order of the parameters still matters.

@IsNotMember means “has no element in common with”. The order of the parameters does not matter.

For example !@IsMember( “1”:“2”; “2”:“3”:“4” ) is true – “1”:“2” is not a subset of “2”:“3”:“4”. But @IsNotMember( “1”:“2”; “2”:“3”:“4” ) is false – “1”:“2” does have an element in common with “2”:“3”:“4”.

@IsNotMember implies !@IsMember, because if the lists have no element in common then one list cannot possibly be a subset of the other.

Subject: RE: 6.5 Bug with !@IsMember <> @IsNotMember ?

hi rod,

thanks for your reply, but shouldn´t it work for

both because i´m looking just for 1 element(@name([CN];@username) in a list of elements?

but its true, when !@IsMember = @IsNotMember

the second fuction wouldn´t be necessary.

ciao

Subject: RE: 6.5 Bug with !@IsMember <> @IsNotMember ?

Then change the order of the parameters in !@IsMember, so that the single element is first.

Subject: 6.5 Bug with !@IsMember <> @IsNotMember ?

The short list should be the first parameter, not the second.Try it this way:

@IsNotMember(@Name([CN];@UserName); (@DbColumn(“”: “NoCache” ; “”:“” ; “setupuser” ; 9))

Subject: RE: 6.5 Bug with !@IsMember <> @IsNotMember ?

thanks for the reply, you are right, but it works also in my case, maybe beacuse it acts like two textlists: @IsMember( textListValue1 ; textListValue2 )

BUT the Problem is another one:

!@IsMember doesn’t act like @IsNotMember

the “!” befor @ismember is a neogation of the formular.

that means the neogation of @IsMember is not the

same anymore like @IsNotMember

i have used the !@ismember in many db´s, so thats that what i m afraid of.