November 4, 2018 at 9:43 pm
Hi all,
So this issue is driving me bat guano insane.
I have MS Access linked to SQL tables.
1. There is no form or any other connection being made to the table. I simply have the table open.
2. I can create a record and at that time of creation, I can add data into any field.
3. Once I leave the record and come back into it, any further editing creates a write conflict error.
4. Based on some research, I have added a timestamp field to the table.
5. I have sacrificed 12 innocent kittens to the gods of Microsoft.
There seems to be no adequate answer to this issue. Can anybody offer a reasonable solution?
Ps. Am something of a noob to the SQL world.
Cheers
November 5, 2018 at 1:45 am
barry.nielson - Sunday, November 4, 2018 9:43 PMHi all,
So this issue is driving me bat guano insane.
I have MS Access linked to SQL tables.
1. There is no form or any other connection being made to the table. I simply have the table open.
2. I can create a record and at that time of creation, I can add data into any field.
3. Once I leave the record and come back into it, any further editing creates a write conflict error.
4. Based on some research, I have added a timestamp field to the table.
5. I have sacrificed 12 innocent kittens to the gods of Microsoft.There seems to be no adequate answer to this issue. Can anybody offer a reasonable solution?
Ps. Am something of a noob to the SQL world.
Cheers
Does the table have a unique primary key?
😎
November 5, 2018 at 4:55 am
What are the fields in the table? Is there a bit (Yes/No field for Access) field?
November 5, 2018 at 7:30 am
barry.nielson - Sunday, November 4, 2018 9:43 PMHi all,
So this issue is driving me bat guano insane.
I have MS Access linked to SQL tables.
1. There is no form or any other connection being made to the table. I simply have the table open.
2. I can create a record and at that time of creation, I can add data into any field.
3. Once I leave the record and come back into it, any further editing creates a write conflict error.
4. Based on some research, I have added a timestamp field to the table.
5. I have sacrificed 12 innocent kittens to the gods of Microsoft.There seems to be no adequate answer to this issue. Can anybody offer a reasonable solution?
Ps. Am something of a noob to the SQL world.
Cheers
I don't know much about access but it sounds like there's a transaction that's been left open by Access. I don't know where "implicit transactions" may be set by Access. Connection string?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2018 at 7:56 am
I used to see this a lot and never figured it out (altho timestamp did help). Somewhere along the way (having upgraded to SQL 2012 and Access 2013) the problem went away.
November 6, 2018 at 2:34 pm
Thanks to all those responded.
I solved the issue by altering all the bits fields to TinyInt fields. This them solved the write conflict issue, but created an issue with using checkboxes, since TinyInt fields are not happy with the recording of -1 values (a particularly silly way Access resolves the difference between true or False) - I had to swap out checkboxes with comboboxes instead. Also, it turn out I didn't need a timestamp after all. It's not a perfect solution, but it works.
Thanks again to all responders.
Cheers
November 7, 2018 at 1:57 am
You can use BIT fields and then set the default value to 0 in SQL. This gets around the issue I have experienced in the past.
Thanks
November 7, 2018 at 2:16 pm
Hi Mark. that's Interesting. Thanks for the tip. I'll look into it. For example can i create the table with the 0 value as the default?
Thanks again.
Cheers
November 7, 2018 at 2:34 pm
barry.nielson - Wednesday, November 7, 2018 2:16 PMHi Mark. that's Interesting. Thanks for the tip. I'll look into it. For example can i create the table with the 0 value as the default?
Thanks again.
Cheers
In SQL Server, yes.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply