Write Conflict when using datasheet view with search

[BonnieG]

I have a few forms - one search form (frm_main_search) which uses a basic datasheet view as a subform (subfrm_main_search), and one form which I launch from the subform (via a double click event) for the user record - frm_user_record.

If I search for a user, then select them from the datasheet view query results, I can launch the user record as frm_user_record.

However if I then change anything on the user's record, I go to search for another user in the database and get the Write Conflict dialog. See my attached screenshot for a view of my form.

I understand why this is happening - I've changed the data of one of the visible records on the data sheet, so it needs to reload the data. However I'd like to suppress this error as I'm dealing with hundreds of these a day and it also confuses some of our less tech savvy users.

I ALWAYS click "Drop Changes" and encourage my users to do this too but is there a way of preventing this dialog from appearing?

 

[pr2-eugin]

I would make the SubForm unbound. In other words, make the Form bound to a Query instead of the table. Or set the Data Edit on the SubForm to False. This will not allow any edits on the SubForm, so this dialog will not keep popping.

 

[BonnieG]

Thanks for that, Paul. I thought your second suggestion sounded a bit easier, so tried that, but I'm still getting the write conflict even when the subform doesn't allow edits?!

Being an Access Amateur I'm not quite sure how to make the subform unbound, so am keen to get your latter suggestion working. I wonder what I'm doing wrong!

 

[BonnieG]

Yes it is AccessBlaster.

 

[BonnieG]

Thanks AccessBlaster... I don't actually have any checkboxes in that table at all. Could you please give me a clue as to what I'm looking for?

I have an AutoNumber field, a large number of Text fields, 4 x Number fields, 6 x Date/Time fields, a Memo field, and that's about it...

 

[BonnieG]

Just wanted to let you know I managed to resolve this after a colleague noticed that one of the events on the form was triggering an "edit" of the datasheet row. Added in an undo of the edit and it fixed the issue. Hurrah!

Thanks everyone.