Joe:
If the entry is NULL, then the results should be
NULL. You are right. I think this is another one that deserves the
'<field>' != $NULL$ treatment.
James McKenzie
L-3 GSI
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Friday, October 13, 2006 11:09 AM
To: arslist@ARSLIST.ORG
Subject: Re: Duplicate Records
Yes,
Scan through the table for conditions that will cause a record to be
duplicate but make an exception to skip records that have a NULL
value in that field. Then if it finds any match, return the Entry-ID of
that record to a temporary field. If at the end of the search the Temp field is
NULL, you know you haven't found a duplicate. If its not NULL return the
duplicate record error you want to return and prevent the save of that
record..
Cheers
Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.
-----
Original Message ----
From: "Sullivan, Neil G CTR USAF AFRL/SNOX" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Friday, October 13, 2006 9:07:56 AM
Subject: Duplicate Records
**
From: "Sullivan, Neil G CTR USAF AFRL/SNOX" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Friday, October 13, 2006 9:07:56 AM
Subject: Duplicate Records
**
Listers,
Is there any way possible to use workflow to check for duplicate records in a form without using a unique index? I can't use an index because some of the values in the field will be null.
Any help is appreciated.
Neil "Sully" Sullivan
Remedy Developer/Administrator
AFRL/SNOX
Wright Patterson AFB, OH
45433
937-904-9788
__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
