Page 1 of 1
Posted: Thu Sep 01, 2005 12:55 pm
by ArndW
Even though I haven't had this problem, I have read in this forum that several people have had problems with this not working correctly.
The recommendation has been to use the fact that upon a failed lookup the columns are returned as NULL and can be detected with a IF ISNULL(Lookup.ColumnName) condition.
Posted: Thu Sep 01, 2005 1:52 pm
by chulett
My Rule Of Thumb is to use NOTFOUND only on hashed file lookups and the old school IsNull check for all other reference lookups.
RE: Problem to use NOTFOUND
Posted: Fri Sep 02, 2005 6:40 am
by shepli
Thanks for all your help.
It seems the NOTFOUND does not always catch the NULL value from a failed lookup. I'll use ISNULL(Lookup.ColumnName) in my job.
Posted: Fri Sep 02, 2005 8:25 am
by kumar_s
I guess moderator could NOTFOUND the server forum and hence moved_to 'looking for talent' 
Posted: Wed Sep 07, 2005 6:18 am
by whardeman
I honestly have no idea how this thread wound up in "Looking for Talent" in the first place if it was not originally posted there by the author. Despite my feeble technical knowledge, I could guess from context that this was not a work advertisement or an appeal for skilled help.
Was this post originally in the Server forum and subsequently moved to Looking for Talent before being moved back? I first took notice of this thread when I saw it in the L.F.T. forum, so I can't imagine who might have moved it there.
It's not of great concern, but it is rather odd.
P.S. Taunt the moderator at your own risk.