Access checkbox and SQL Server bit

[Tim]

I add 4 check boxes on a new form. These checkboxes are bound to a table that
have 4 bit values (linked from SQL Server). When I click on the Field list
and drag them to the form, these fields become textboxes (not bit). Why?
Also, when I click on a check box and move to the next record, there is a pop
up error message saying that this record has been changed by another user....

My question is how can I create checkbox(es) on Access form that are bound
to bit(s) values. Thank you for your help.

 

[Albert D. Kallal]

I add 4 check boxes on a new form. These checkboxes are bound to a table
that
have 4 bit values (linked from SQL Server). When I click on the Field list
and drag them to the form, these fields become textboxes (not bit). Why?
Also, when I click on a check box and move to the next record, there is a
pop
up error message saying that this record has been changed by another
user....

My question is how can I create checkbox(es) on Access form that are bound
to bit(s) values. Thank you for your help.

I suspect that your data types on the sql server side are "real" data types,
and are NOT correct.

So, you have to be careful and not have the sql server table setup
correctly.

Your problem is likely explained here:

ACC2000: Write Conflict Error When You Try to Update Records in a Linked SQL
Server Table

http://support.microsoft.com/?id=280730

If your data type for field are correct, then you still need to set their
defaults on the sql server side as 0 to avoid the above message...

You should in addition the above have a primary key exposed, AND ALSO THE
TIMESTAMP field exposed. (ms-access uses that timestamp field to determine
if the record has been changed...if not, then ms-access has to do a field by
field compare..and can get confused).

So, check the first issue (set default of those fields = 0, not left to be
null), and if that don't work, then check the pk, and timestamp field...

As for dragging on the check boxes, are the sql server fields atually yes/no
(true/false) fieods or are they just simply tinyInt fields or whatever?

Really, use intenger, or use a true/false. With super sized mega disks these
days, I cna't think of ANY reason to play around with nibble, or byte sized
fields anymore...