June 20, 2018 at 5:13 pm
Hey guys,
I have this annoying with Microsoft Access and Microsoft SQL when it comes to constantly getting this annoying prompt message of write conflict. Problem is that it can be hindering when writing data and keeps getting prompt error message of write conflict. I checked in google that if you add timestamp column that it would solve the problem. I added the timestamp column and I can see changes go into the fly..however I do not know how to have access access the timestamp column and write to it without causing a conflict issue. Problem with the timestamp column it is consider a binary in access and in the SQL side it is bunch of hexidecimal.
Any advice would be greatly appreciate it 😀
June 20, 2018 at 6:38 pm
xboxown - Wednesday, June 20, 2018 5:13 PMHey guys,I have this annoying with Microsoft Access and Microsoft SQL when it comes to constantly getting this annoying prompt message of write conflict. Problem is that it can be hindering when writing data and keeps getting prompt error message of write conflict. I checked in google that if you add timestamp column that it would solve the problem. I added the timestamp column and I can see changes go into the fly..however I do not know how to have access access the timestamp column and write to it without causing a conflict issue. Problem with the timestamp column it is consider a binary in access and in the SQL side it is bunch of hexidecimal.
Any advice would be greatly appreciate it 😀
You wouldn't write to a timestamp column - it is updated automatically. You'd get an error if you try to update it.
Sue
June 20, 2018 at 9:40 pm
Sue_H - Wednesday, June 20, 2018 6:38 PMxboxown - Wednesday, June 20, 2018 5:13 PMHey guys,I have this annoying with Microsoft Access and Microsoft SQL when it comes to constantly getting this annoying prompt message of write conflict. Problem is that it can be hindering when writing data and keeps getting prompt error message of write conflict. I checked in google that if you add timestamp column that it would solve the problem. I added the timestamp column and I can see changes go into the fly..however I do not know how to have access access the timestamp column and write to it without causing a conflict issue. Problem with the timestamp column it is consider a binary in access and in the SQL side it is bunch of hexidecimal.
Any advice would be greatly appreciate it 😀
You wouldn't write to a timestamp column - it is updated automatically. You'd get an error if you try to update it.
Sue
The problem I was getting these errors because in my SQL server side there where no columns with timestamp. So I was researching on google and someone said to add a column with timestamp and that fixed the problem. So I did. The problem did not get resolved. Other people suggested not to have your controller bounded but that could be a problem in the long wrong and opens an enormous project. Do you have any other suggestion, please?
Thanks in advance.
June 21, 2018 at 7:01 am
xboxown - Wednesday, June 20, 2018 9:40 PMSue_H - Wednesday, June 20, 2018 6:38 PMxboxown - Wednesday, June 20, 2018 5:13 PMHey guys,I have this annoying with Microsoft Access and Microsoft SQL when it comes to constantly getting this annoying prompt message of write conflict. Problem is that it can be hindering when writing data and keeps getting prompt error message of write conflict. I checked in google that if you add timestamp column that it would solve the problem. I added the timestamp column and I can see changes go into the fly..however I do not know how to have access access the timestamp column and write to it without causing a conflict issue. Problem with the timestamp column it is consider a binary in access and in the SQL side it is bunch of hexidecimal.
Any advice would be greatly appreciate it 😀
You wouldn't write to a timestamp column - it is updated automatically. You'd get an error if you try to update it.
Sue
The problem I was getting these errors because in my SQL server side there where no columns with timestamp. So I was researching on google and someone said to add a column with timestamp and that fixed the problem. So I did. The problem did not get resolved. Other people suggested not to have your controller bounded but that could be a problem in the long wrong and opens an enormous project. Do you have any other suggestion, please?
Thanks in advance.
You quite literally CAN NOT touch that column from MS Access. You just have to have it exist. If you INSERT to the table, do NOT include that column in your INSERT. When you SELECT from that table, don't waste the time including it there either. And of all the things that can cause you grief, this is much less than the problems you run into with bound controls. For heaven's sake, if you have bound controls, do NOT have one for the timestamp column. This is NOT an option, but a necessity., First question is whether the SQL Server table has a primary key. If it does not, you'll have no way to update the table from within Access. Also, the most grief in Access is usually because of bound controls. Yes, there's a lot more VBA needed to deal with unbound ones, but in the long run, the gain in productivity and flexibility of functionality is usually well worth it. Plus you learn a heck of a lot more in the process.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 22, 2018 at 11:34 am
sgmunson - Thursday, June 21, 2018 7:01 AMxboxown - Wednesday, June 20, 2018 9:40 PMSue_H - Wednesday, June 20, 2018 6:38 PMxboxown - Wednesday, June 20, 2018 5:13 PMHey guys,I have this annoying with Microsoft Access and Microsoft SQL when it comes to constantly getting this annoying prompt message of write conflict. Problem is that it can be hindering when writing data and keeps getting prompt error message of write conflict. I checked in google that if you add timestamp column that it would solve the problem. I added the timestamp column and I can see changes go into the fly..however I do not know how to have access access the timestamp column and write to it without causing a conflict issue. Problem with the timestamp column it is consider a binary in access and in the SQL side it is bunch of hexidecimal.
Any advice would be greatly appreciate it 😀
You wouldn't write to a timestamp column - it is updated automatically. You'd get an error if you try to update it.
Sue
The problem I was getting these errors because in my SQL server side there where no columns with timestamp. So I was researching on google and someone said to add a column with timestamp and that fixed the problem. So I did. The problem did not get resolved. Other people suggested not to have your controller bounded but that could be a problem in the long wrong and opens an enormous project. Do you have any other suggestion, please?
Thanks in advance.
You quite literally CAN NOT touch that column from MS Access. You just have to have it exist. If you INSERT to the table, do NOT include that column in your INSERT. When you SELECT from that table, don't waste the time including it there either. And of all the things that can cause you grief, this is much less than the problems you run into with bound controls. For heaven's sake, if you have bound controls, do NOT have one for the timestamp column. This is NOT an option, but a necessity., First question is whether the SQL Server table has a primary key. If it does not, you'll have no way to update the table from within Access. Also, the most grief in Access is usually because of bound controls. Yes, there's a lot more VBA needed to deal with unbound ones, but in the long run, the gain in productivity and flexibility of functionality is usually well worth it. Plus you learn a heck of a lot more in the process.
Thank you so much!! You guys are awesome!
June 22, 2018 at 12:46 pm
xboxown - Friday, June 22, 2018 11:34 AMThank you so much!! You guys are awesome!
You're very welcome.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply