Hi Garret,

Remember we talked about that, and I TOTALLY agree. My purpose in the sample code was to show the problem. However, if you look at almost all code from books, MS, magazines, and here you will find that rarely if ever is REQUERY used in the lnResult=REQUERY(lcAlias) mode.

As for our own shop, we do check return values. That is why it was so hard to get to the bottom of this, since we were only hitting the error 2% of the time. If you lose the return value i.e. =REQUERY(), you can reproduce the problem much better.

That is the ONLY reason we didn't check for return values in the sample code. Garret, this bug was a a be-atch to reproduce, so I wanted to be as clean as possible. Had I used lnResult=REQUERY(lcAlias), you might not have seen it to begin with....it takes alot more effort. However, I can tell you that with a live deployment, lnResult=REQUERY(lcAlias) and IF REQUERY(lcAlias) < 1 fails enough for the users to notice.

Cheers,
Bob