Yeah, i tried that and for some reason the only thing that worked for me was to assign it to a button. That is ok, it is easy enough to do
Competent Performer
Windows 7 64bit 
Access 2010 32bit
Yeah, i tried that and for some reason the only thing that worked for me was to assign it to a button. That is ok, it is easy enough to do
Virtually Inert Person
Windows 10 Access 2016
That will make the field a lookup field in the table. Allen Browne actually suggested doing that??
EDIT - took a look. One has to remember that AB's site uses really outdated information (even though it's still great). I'm thinking that his point was it was available on the lookup tab so it should have been an option on the property sheet. However, a yes/no field automatically provides a checkbox in the table field so I don't get where that is coming from. Maybe it wasn't always so?
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Competent Performer
Windows 7 64bit Access 2010 32bit
yes, after doing what he suggested it seems that it is really now different. If I upsize the field into SQL server, which was my main concern, it still does the same thing and creates a number field with 0 as false and 1 as true and still reads correctly in Access with the 0 being false and -1 being true. Just like a regular yes/no made in access.
I think his main point was to make that field an actual number field which is better for certain queries.
Posting Permissions
Reply With Quote