Write Conflict

[Mark A. Sam]

Hello,

I added fields to a linked SQL Server table and getting a Write conflict
message when updating the table. The problem occurs then I refesh the link.
In an older copy of the database the problem doesn't exist until I refresh
the link.

The fields I added were simply bit fields with Default of 0. I deleted the
fields and added the default value in hopes of resolving the problem.

I added the same fields (no default value) to another table which has not
caused any problems.

It think it is SQL Server 2000 (around that time)
Windows Server 2000
Access 2000

Thanks for any help and God Bless,

Mark A. Sam

 

[Gina Whipp]

Mark,

Instead of refreshing the link, try recreating it. At least, that worked
for me...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Mark A. Sam]

Gina,

I had tried that. That didn't help.

I resolved it however. For some reason, the [Allow Null Values] property on
those new fields needed to be set to False. I don't know why. There are
other Bit type fields in that and other tables with the property set to
True.

God Bless,

Mark

 

[Gina Whipp]

Mark,

There are several *discussions* out there about Bit fields as they relate to
SQL Server. As I read your reply it jogged a memory about Bit fields being
False on SQL Server and are never actually Null, so allowing nulls is really
not an option.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Gina,

I had tried that. That didn't help.

I resolved it however. For some reason, the [Allow Null Values] property
on those new fields needed to be set to False. I don't know why. There
are other Bit type fields in that and other tables with the property set
to True.

God Bless,

Mark

Mark,

Instead of refreshing the link, try recreating it. At least, that worked
for me...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Mark A. Sam]

Gina,

Graham Seach responded about this on the Professional Microsoft Access
Developers' Network on LinkedIn. He said that disabling Nulls would cause a
problem which makes sense, since the other bit fields are enabled. But this
is backward, which is why I couldn't resolve it much earlier.

God Bless,

Mark

Mark,

There are several *discussions* out there about Bit fields as they relate
to SQL Server. As I read your reply it jogged a memory about Bit fields
being False on SQL Server and are never actually Null, so allowing nulls
is really not an option.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Gina,

I had tried that. That didn't help.

I resolved it however. For some reason, the [Allow Null Values] property
on those new fields needed to be set to False. I don't know why. There
are other Bit type fields in that and other tables with the property set
to True.

God Bless,

Mark

Mark,

Instead of refreshing the link, try recreating it. At least, that
worked for me...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

http://www.regina-whipp.com/index_files/TipList.htm

Hello,

I added fields to a linked SQL Server table and getting a Write
conflict message when updating the table. The problem occurs then I
refesh the link. In an older copy of the database the problem doesn't
exist until I refresh the link.

The fields I added were simply bit fields with Default of 0. I
deleted the fields and added the default value in hopes of resolving
the problem.

I added the same fields (no default value) to another table which has
not caused any problems.

It think it is SQL Server 2000 (around that time)
Windows Server 2000
Access 2000

Thanks for any help and God Bless,

Mark A. Sam