Chris,
Strange. You could do a VALIDATE DATABASE on the suspicious DBC. Also reindexing might be a good idea.

>Daniel - thanks for your help!
>
>Right I have narrowed it down...
>
>This problem only occurs with all tables in one .DBC - other tables in other .DBCs act normally...
>I am using the Microsoft Visual Foxpro Driver and the version of Query is whatever ships with Office 2K...
>
>The values show in Query as 1s and 0s...
>
>I think it has to be something to do with the .DBC...
>
>Any ideas?