The checkbox is the last column on a grid whose recordsource is a VFP cursor. I've previously found that having a select statement for a VFP cursor with ".F. as check" allowed the user to check/uncheck although the cursor is read-only. Now that the remote database does not have logical fields/literals, I tried "0 as check" and failed. The value of the checkbox(VFP base class) is always initially set by the cursor's select statement.

>The docs claim that a checkbox can be numeric, integer, or logical. As a reality check, you can do this:
>
>

>1. Create a form with a checkbox on it
>2. DO MyForm Name MyCheckBoxTest
>3. ? MyCheckBoxTest.Check1.Value, which should return 0
>4. Check the box
>5. Repeat step 3, you should get a  1.
>

>
>Are you anywhere assigning the value of the checkbox in code? Have you subclassed the checkbox and assigned it a logical value?


>>Hi, in a select from a remote (non-VFP) table into a local cursor I include '0 as check'. In the grid the checkbox is unchecked but as soon as it is clicked it complains bitterly of 'data type mismatch'. Debugging shows the cursor field 'check' as being numeric which I believe is a valid data type for a checkbox. Can anyone help?
>>
>>PS. Selecting from a VFP table using '.F. as check' works fine, unfortunately the database being used does not have logical fields/literals.