[AccessD] Write Conflict

Do you think that will help?  When the main form moves to a new record is
when the write conflict occurs.  

R

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson
Sent: Wednesday, April 02, 2014 8:01 AM
To: Access Developers discussion and problem solving
Cc: Off Topic
Subject: Re: [AccessD] Write Conflict

Can you dissociate the child form in the before update event of the main
form and reassert it in the after update event?
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
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com