>>
Have you considered using a computed field that merges all 4 fields and
then
create a "unique" rule for the computed field? I am just not sure you can
have rules for computed fields...at least, I have never used rules in
computed fields ...maybe someone else can chime in...
<<
Rules on computed fields DO works : here is an example :
CREATE TABLE case1 ( +
grpays TEXT (2) NOT NULL ('Indiquer le groupe de pays'), +
cregdou1 TEXT (1) NOT NULL ('Indiquer la proc�dure (1er car. du
r�gime douanier)'), +
cmodtran TEXT (1) NOT NULL ('Indiquer le mode de transport'), +
cp TEXT (3) , +
scase1 TEXT (3) NOT NULL ('Indiquer la valeur � affecter � la case
1 du DAU'), +
scase3 TEXT (5) , +
clecase1 = (grpays + cregdou1 + cmodtran + cp) TEXT 7 NOT NULL +
)
.....
RULES 'Cas d�j� r�pertori�' FOR case1 SUCCEEDS +
WHERE (clecase1 IS NOT NULL AND clecase1 NOT IN +
(SELECT clecase1 FROM case1 T1 WHERE T1.clecase1 = case1.clecase1))
I wander now why I did't set column 'clecase1' a PK ....
It would have been a must better solution in this case ....
J.M. GRATIAS, Logimatique
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
