hello (1 Viewer)
- Thread starter mukiibi
- Start date
- Local time
- Today, 11:06
- Joined
- Jul 9, 2003
- Messages
- 16,271
- Local time
- Today, 05:06
- Joined
- Feb 28, 2001
- Messages
- 27,140
mukiibi, welcome to AWF.
When Microsoft can't find something, only a few reasons apply.
First, the object in question might not be spelled correctly. But I've got to admit, "NO" doesn't look like a wrongful spelling.
Second, the object is used in an incorrect context. I think this is more likely in your case. Please be aware that I am GUESSING, but I would think you tried to assign a value to a "YES/NO" field by saying something like:
If this is what you did, then there is a little "gotcha" in the documentation and you didn't read up on it completely. A YES/NO field isn't really yes or no. It is TRUE or FALSE, both of which are keywords for Boolean values. You might try to find where this happens (if my guess is correct) and assert a value of FALSE rather than NO. Because Access has TRUE and FALSE but it doesn't have YES and NO in that context. That would account for the missing object.
When Microsoft can't find something, only a few reasons apply.
First, the object in question might not be spelled correctly. But I've got to admit, "NO" doesn't look like a wrongful spelling.
Second, the object is used in an incorrect context. I think this is more likely in your case. Please be aware that I am GUESSING, but I would think you tried to assign a value to a "YES/NO" field by saying something like:
Code:
[YNfield] = NoIf this is what you did, then there is a little "gotcha" in the documentation and you didn't read up on it completely. A YES/NO field isn't really yes or no. It is TRUE or FALSE, both of which are keywords for Boolean values. You might try to find where this happens (if my guess is correct) and assert a value of FALSE rather than NO. Because Access has TRUE and FALSE but it doesn't have YES and NO in that context. That would account for the missing object.
