>I may be wrong on this but if I'm not mistaking lUnique is there from the days of CodeBook.
>
>I understand your concerns about not using the bizobj to do your work but on the other hand minor rule validations can be performed by the client without breaking any n-tier architect design. In this particular case you're still not touching the data directly but you're actually working with a cursor (a typical data format as oppose to ado or xml). Although, it can come back and bite you in the ???.
>
>But I do feel your concerns about this. Just be careful how you use it. My suggestion would be only to use for very minor rule validations. Not anything major.

Your comments are alomst correct. The lUnique logic is unique to MM and has been there since early 3.0 releases. (As far back as I can remember) If a control is marked lUnique = .t., then a search view is used to look up the value before it is placed in the primary cursor. This most cetainly breaks n-tier design. The control UI should not know anything about the business rules. Validation for uniqueness should be done in bizrules object.