Microsoft Access / SQL database

Question

I have an SQL database, with an Access front end that has been working fine for many years.

I wanted to add a check box to one of the access forms (very similar to one already there, but labelled differently)

I added the new column to the SQL database table (Table = ChangeNote, Column = InstService)

As per an existing check box, this was set up as a YES/NO (check box)

I then added the new column to an existing query that cross-referenced 2 tables.

I then added the new check box to the form and set the control source to InstService (All exactly the same as the working check box already in the form [I cross referenced all properties])

However, now it seems the changes made have 'locked' the database table. Whether through the form or directly in the table, as soon as I input data and tab out a get the 'Write Conflict' error. why is this happening?

• No-one else is using this database
• Permission are all correct.
• If I remove the query input, it works ok, but does not work as a check box.

Scratching my head here, what am I missing!!!????

Andy

Answer 1

Scott M. nailed the answer.

I try to avoid the bit field usage. Consider using a smallint or some other numeric field that offers the same functionality. One of the benefits to smallint is WHEN users are no longer happy with simply yes/no and need to select from several options you won't need to change data types.

Answer 2

SQL databases don't have a Yes/No (or Boolean) datatype. You probably setup a Bit data column, and must set a Default value for the column, and also update all existing records to have a non-null value.

You can define a value of 0 for the default (0 = False)

You can then update all rows in that table to False:

UPDATE ChangeNote SET InstService=0