Problem to use NOTFOUND

[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.

[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.

[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.

[kumar_s]

I guess moderator could NOTFOUND the server forum and hence moved_to 'looking for talent'

[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.