How can I find the source of a Write conflict? 3

[steve728]

Where can I read/learn how to detect the source of a stinkin Write Conflict. I'm using Access 2002 on a single
work station. What are some typical things to look for?
This is a headache I haven't been able to get rid of!!$%$#@

Steve

 

[KenReay]

Hi

Ar eyou saying that using a single user database on one PC you are getting a write conflict?

If yes:

Do you have two (or more) instances of the db open at one time

Are you doing something like updating a bound form (via the controls) and aklso updating the table(s) on which the bound form is based, either via SQL or via recordset .Update

A write conflict is caused when user A read a record with the intention of updating it, applies some chnages, then finds that when they come to write it back to disk another user has updated the same record in the period of time between teh first user reading it, and being ready to write it back.

Keep in mind that unless you have specifically set row level locking, then 'record' means a databse page (4096 bytes I think) ratehr than the single row you might expect.

You can also apply pessimistic locking, which locks the row on red rather on write, but this will impact concurency

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[pdldavis]

Hi, I got this error after a field update and I did not save the record - still in edit mode - basically the same thing Ken is describing. What I did was after the update I used a docmd.runcommand acCommandSaveRecord. Solved the problem for me.

 

[steve728]

Thank you folks. Yes change made to the same table needed a few seconds to complete. I used a 5 second "Please Wait" delay screen to solve the issue.

 

[LonnieJohnson]

Hello. I am having this same problem with a linked SQL Server table. I have kicked everyone out of the Accesss front end. Instead of going through the form, I am trying to update a record at the table level via access and still am getting this message. Any thoughts?

ProDev, MS Access Applications
Visit me at ==>

http://www.prodev.us

Contact me at ==>lonniejohnson@prodev.us

May God bless you beyond your imagination!!!

 

[pdldavis]

Hi, thanks for the Star! There are a boatload of those docmd.runcmd commands in vb. In the code builder, simply type in docmd.runcmd and hit the space bar . That should give you the entire list. There are a number of them you would probably find useful at one time or another.

 

[Nowell]

Lonnie,

Are you using Access project with SQL server?
What is the data type of the field you are trying to update?

 

[mmaddox]

I know this is an old thread, but here's how I solved it for myself : It is explained in Microsoft support article ACC2000: Write Conflict Error When You Try to Update Records in a Linked SQL Server Table
View products that this article applies to.
This article was previously published under Q280730.

It was a problem with Bit data types - used for check boxes. Solved by either adding a default value on the SQL table, or datestamp field.

 

[LonnieJohnson]

Thanks mmaddox. I actually remember that being the fix that I eventaully used. Then we had it come up again last week and we couldn't remember what we did. That was right on time.

ProDev, MS Access Applications
Visit me at ==>

http://www.prodev.us

Contact me at ==>lonniejohnson@prodev.us

May God bless you beyond your imagination!!!

 

[WantsToLearn]

Thanks mmaddox! I was going nuts over this issue. Here is the link referred to above for anyone's benefit:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;280730