Simple Tid Bit
If you’re using Access as a front-end for a Sql Server database and you decide to use the Sql Server bit data type for say, a yes no field. Do remember to give your field definitions a default value first or you will run into problems on the Access side. Access will notify you that …this record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes… every time you attempt to edit an existing record. In my case the option to save the record was disabled. I simply changed the default value for all my bit fields to 0 and everything worked fine. NULL strikes again!
The funny thing is that I’ve used Access as a front end like this before (many times) and never had this problem. Turns out that in the other cases where I used the bit data type, I created a value for the bit field in the application at record creation time. I sort of felt like a newbie today. NULL strikes again!