Debug stepping missing statement that seems correc

Topic

New Reply

Post deleted by jp2558

Reply | Quote

Replies

Hello,
Have you tried to use ISNULL as in:
–> If ISNULL(Me![CreditCardNumber]) Then
Null has given me headaches but I always forget the workings of Null before the next use.
Good Luck

Reply | Quote

Dana’s suggestion is a good one. You can’t test for anything being equal to Null, because Null represents an absence of a value and the comparison will always return false. You have to use the IsNull function for that purpose.

Reply | Quote

Thank You, Thank You, Thank You. This has fixed the problem and now the cursor goes where it should depending on the field in error. How did you (both Dana & Charlote) learn these things? Where can I find the suggested syntax for such statements so that I don’t keep chasing my tail using what appears to be acceptable code?

Reply | Quote

I agree – remembering how to work with nulls takes some getting used to (although as I said in a previous message, explicit numeric nulls can be extremely useful in certain circumstances). It is documented in the online docs (although you might need some psychic talent to realize beforehand what you should be looking up ) – see “Comparison Operators” in the online docs.

When you need to work with nulls, keep the function nz(…) in mind; very handy where you do want to treat null as zero (or any other chosen value) in a specific place in your code.

Reply | Quote

Well, it helps when you start with Access 1.0 the day it’s released and “grow up” with it as it evolves!

Reply | Quote

The best place for finding things like that is the WOPR lounge. By trying to understand the questions asked and seeing the answers to them you learn a lot. And you may be able to help someone else too.

Reply | Quote