Write Conflict After Update to 2010

[cnelson]

I have run into an issue when updating from 2010 to 2007. I have rolled back to 2007 and do not experience these issues. However, when I update to 2010, I do receive these issues.



The problem exists when modifying data and closing a form. I receive a “Write Conflict” message. It states, “This record has been changed by another user since you started editing it.” I am the only user in the application.

The form has several sub forms. My assumption is that the data is being saved multiple times on the form, causing a “dirty read”. I could update the application to work around this issue. However, since I did not write this application, I would prefer not to do this.

Since I have isolated this issue to be a problem related to the update from 2007 to 2010, I have to believe that somebody else has had this issue.
Does anybody have any suggestions?

[RuralGuy]

Try making sure all of the forms and SubForms involved a using queries rather than tables directly.

[cnelson]

At this point, I cannot propose to the client saying this “May” fix your issue and will cost x amount of dollars. This would probably be a major overhaul to the application. Since this is only happening in 2010, I still believe this may be an issue with not setting up the install of 2010 correctly. Any other suggestions?

[RuralGuy]

As I'm sure you are aware, each release of any product "fixes" issues found by programmers when opening modules of the system for the upgrade code. This almost always has unintended consequences and is generally pointed to as a "bug". In reality, the newer release is almost always more sensitive to, and less forgiving of, the methodology of the coding. Have you at least assertained whether the Forms and SubForms are using tables directly or queries? Queries solve a lot of the locking issues reported.

[BStrong]

I am experiencing the same 'Write Conflict' issue with my SQL Server BackEnd and Access2010 FrontEnd app. Form has no subforms and RecordSource is an SQL SELECT qry. I have removed all combo boxes (that were value list based) and have only one combo box remaining whose RecordSource is also an SQL SELECT qry. Still get the Write Conflict message (copy/drop changes). I'm leaning toward believing it has something to do with the SQL Server data table. I added some fields prior to this issue occurring. Any thoughts?

[BStrong]

HALLELUJAH...I found the resolution to my Write Conflict problem through this article...Need Timestamp Field in SQL Table