Thank you Mary,

I appreciate your comments and recommendations.

> The timestamp columns help Access resolve concurrency issues, so you
> don't have to do anything special to get the benefit. However, for
> unbound forms, you'll need to handle concurrency yourself either using
> timestamps or by impelmenting concurrency manually (described in
> book).

I don't think concurrency is a problem, so I will try other solutions first.

> One suggestion -- since money is tight, consider not doing the app
> unbound --

To start with, most forms are bound and displays only one record, the
problem seems to be limited to the two forms that are unbound.

Unortunately, due a unique sequence of operations involving a code
generated key index, which are also sent to a bar code printer, the
problem forms have to be unbound.

So far the problem appears to affect only the checkbox controls
which are based on Access Yes/No fields. Since these fields were
converted to Bit data type in SQL Server by the Access 2002
Upsizing Wizard, I am working on the assumption that this is the
root of the problem, possibly because I had used DAO recordsets.

I am working on converting the DAO recordsets to ADO and at the
same time adding code to explicitly convert the boolean data between
the VB True/False format to to the Bit type data data 1/0 format.

Ragnar