Table locked with ODBC

[Guest]

Hopefully some here can assist me on this or least point me in the right
direction.

Here goes...

I created an application that both interacts with an Access program and a
..Net web program. The database itself is on a SQL Server2000 machine. The
Access portion will be on a few machines. And of course the web interface.

Now I can interact with the database through the web, fine. I can also
interact with it on the SQL Server. However, I have just one table that
keeps preventing me to interact with on the Access front-end. I can not
delete a record nor update/edit it. I am using and ODBC connection to the
SQL server to utilize it.
I even deleted all the relations thinking that would be cause the problem,
but no go.
I rebooted the server, but no go. I even imported my forms, modules, etc
into a new database, but no go. I believe it has something to do with the
actual Access DB.

Can someone shed some light why this would be happening? Thanks a bunch in
advance

 

[Guest]

Well I think I found the problem. I have a few bit fields in the SQL
database table. When I look in the table in Access it automatically sets
them to 0 even though I don't have a default value set for them in SQL
Server. Even if I make the default value equal to (''), it still paces a 0
in the field on the Access table side.

After changing them to char fields I was able to update, delete, edit this
table without any problems. Now I need these fields default set null, but
need them as boolean (bit) type.

Does anyone have a solution on how to resolve this?

Thanks in advance

 

[John Vinson]

After changing them to char fields I was able to update, delete, edit this
table without any problems. Now I need these fields default set null, but
need them as boolean (bit) type.

I believe that these are incompatible requirements. IIRC the Bit
datatype is not nullable - its only allowed values are 0 and 1. The
zero length text string '' would certainly NOT be acceptable.

John W. Vinson[MVP]