Field type corruption?

[BillCo]

I've searched through the archives and haven't found anyone with
anything remotely like this problem, so I'm expecting (hoping) the
cause is my own stupidity - otherwise I may have a corruption of some
sort!

I have a table with a field that is defined as text, 50 chars - all the
usual default setup. At creation I added a few records and entered text
into the field for each, no problem.

Today, when tracing a weird problem I opened the table to find that the
field is now displayed in table view as a check box. The design view
still maintains that the field is a text field. It seems to have become
a strange hybred field containing both yes/no ints and character
strings. Compact/repair has no effect.

Extracting the values from the field from code pulls '0' from two
records but pulls the original text value from 1 record (there are only
three records). The table is usually accessed via a link to the
backend, but it maked no difference whether you look in the backend or
a frontend. The field is not a PK. The database is in Access 2000.

Any suggestions?

[Dean]

Does this happen on all PC's?

Have you tried deleting all the records, compacting, and re-enter?

[BillCo]

It happened on the backend - the frontends are pulling across the
faulty table def over a link. My concern isnt so much fixing the
problem - I could delete and re-build the table, but I really want to
figure out whats going on in case this is part of a larger problem

[BillCo]

Just as I was hoping - it was my own stupidity!!!
*somehow* the display control property on the field was changed to
"106". Browsing the data in the table then caused access to assign
boolean ints to the underlying data.