Write Conflict in continuous Form

pinkandthebrain · July 15th, 2003, 05:19 PM

I have an Access Project that sets the RecordSource property to an SQL statement. Everything works well until I decide to change the value of a field twice ... Write Conflict, this record has been changed by another user.. etc. I'm the only User, so this should not be a problem. If I change the RecordSource property to reference an SQL Server Stored Procedure, it works. How do I get around this problem as I need to execute different SQL statements from code?
Help would be appreciated. Thanks.

shepston · July 17th, 2003, 11:51 AM

I am inclinded to think the form is not updated or refreshed before you try to change it again. I would start by adding:

Code:

Me.Refresh

in the AfterChange event for the field you are changing. See if that helps. If not, I will need more details to better help trace the cause.

-Shay Shepston

pinkandthebrain · July 18th, 2003, 11:16 AM

I decided to go with the Stored Procedure and Parameter option, as I do not run into any update problems.