Wow. I did some tests with IF statement, BETWEEN() and SET FILTER TO and was surprised to find that even though the result of comparisons is .NULL. it is treated as NOT .T., so for all practical purposes it behaves as .F. which is appropriate. I expected VFP to give an error in the tests above, and don't know where I got that idea. Did VFP use to give error in previous versions?

This data will be used with VB.NET. Do you know if VB.NET behaves is a similar, reasonable, manner?

Thank you for the help,

Alex



>Hi Alex,
>
>It's a kludge and I don't like kludges when there's other way. I'm not sure why would you check for null everywhere?
>
>>Thank you, Sergey. That seems the most "correct" way, since it is an unknown value, but what about having to check for null everywhere? Would using 01/01/1900 (or any other date) make any sense to you?
>>