Bill Benson
bensonforums at gmail.com
Wed Apr 2 10:41:03 CDT 2014
Not only was my early response unlikely to have any merit, but I am all the more embarrassed finding I must take a chance this may make a repeat appearance. I got a response back telling me my reply was awaiting moderator admittance because some freakish cc was in the address ... Anyway in the event that Dan's method does not solve your issue, you can have my swag here: I have in these situations tried (usually works) to change the record source of the subform control to blank, in the before update of the parent, then reset it as it was in the after update. I do not recall the complete mechanism nor why it was really required. There may too have been some code to help me retain, then find again, the subform's position and reapply any filtering that might have been present (the latter being the biggest PIA) Btw (and this some new verbiage) I wonder if your situation would be benefited by using John's class module methods. On Apr 2, 2014 10:45 AM, "Rocky Smolin" <rockysmolin at bchacc.com> wrote: > Dear List(s): > > I have a form with a subform - both bound - to different tables - > parent/child - linked Main form PK to subform FK - standard stuff. > > When I change the quantity of one of the fields of the subform, a quantity > field on the parent form gets updated. All looks good until I try to move > the main form to a new record. Then I get the Write Conflict message - > Save > Record, Copy to Clipboard, Drop Changes. I can see that if I Drop Changes, > the quantity field on the Main form reverts to its original value. If I > click Save Record, all is well. But I need for that message to go away. > > How to I work around this message? > > MTIA > > Rocky > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >