cant edit in my form, write conflict problem?

[Guest]

I have SqlServer 2000 as back end and Access 2003 as front-end. All
tables from Sqlserver are linked to Access 2003. I am having write
conflict problem with one of my forms which is a datasheet sub form to a
main form. The data source of that form (datasheet) is one query based on one
table.
While the form is open I am modifying the data manually sub form and getting
the following message:

Write Conflict

This record has been changed by another user since you started editing
it.............

I have checked the Microsoft technet and here are the steps that I took to
try to resolve this issue yet it is still there.

1) from the menu bar: Tools>Options>Advanced, changed the ODBC refresh
intervals to about 1 sec.
2) I placed the follwoing code in the subform afterupdate event:
me.parent.requery

none of these steps worked! I still get the same error message and I do not
seem to be able to enter any thing.
there is no one else editing the db except me, the form has only one table
in the query. I seem to be able to enter data using code but not manually.
Any Idea?
thanks
Al

 

[John W. Vinson]

I have SqlServer 2000 as back end and Access 2003 as front-end. All
tables from Sqlserver are linked to Access 2003. I am having write
conflict problem with one of my forms which is a datasheet sub form to a
main form. The data source of that form (datasheet) is one query based on one
table.
While the form is open I am modifying the data manually sub form and getting
the following message:

Write Conflict

This record has been changed by another user since you started editing
it.............

Sounds like your mainform and subform - or perhaps your subform and some
*OTHER* form - are both attempting to edit the same record. No can do! What
are the Recordsources of the main and subforms?

John W. Vinson [MVP]

 

[Guest]

Totally different tables. I found the solution and I would like to put it
here so may be it can help some one else with similar problem. The problem as
Microsoft stated is that if the data type for one of the fields in the sql
server table was a "bit", you must assign a default value as (0) other wise
when you are editing/adding data from Access front end, it tries to write
null to it and that triggers the message of write conflict. I went immediatly
and did that and it worked instantly
here is the link:
http://support.microsoft.com/kb/280730
al