[AccessD] Write Conflict

It is set to update the table. However, it doesn't matter what I set to 
happen in the subform because the error message happens when the other form 
is closed and before the subform is accessed.

At 11:28 PM 31/12/2005, you wrote:
>Hi David, and Happy New Year to you too.
>
>It sounds as if the "new form" on which they change rental type is updating
>the same table that your subform is based on. If so I'd try 2 things.
>Firstly do a Save of the subform before opening the new form, and then
>Requery the subform when the other form closes.
>
>-- Andy Lacey
>http://www.minstersystems.co.uk
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > David & Joanne Gould
> > Sent: 31 December 2005 12:09
> > To: accessd at databaseadvisors.com
> > Subject: [AccessD] Write Conflict
> >
> >
> > Firstly, I would like to wish everyone on the a Happy and
> > Prosperous 2006.
> > May the best of 2005 be the worst of 2006.
> >
> > My problem is I am working on a video library database. My
> > hire form has a
> > main form (hirer's details) and a subform (hiring details).
> > There is a
> > combo box that the user uses to select the movie. If they
> > double-click on
> > the combo box they are taken to a new form where they can
> > change the rental
> > type for the movie (eg is it an overnight, 3 nights, weekly
> > etc rental)
> > When they have selected the new rental type the program
> > checks for every
> > instance of that movie name and changes it to the new rental
> > type. It also
> > updates the Hiring record to record the new date due into the
> > table. This
> > all works perfectly. However, when they close the form to go
> > back to the
> > Hiring form, I get Write Conflict. If I click on the Save
> > option it works
> > perfectly and updates the row in the Hire form details to reflect the
> > changes and I can continue to work.
> >
> > I can't seem to figure out where the error is being triggered
> > so I can tell
> > it to save programatically and leave the user none the wiser.
> >
> > Any help in this will be greatly appreciated.
> >
> > TIA
> >
> > David
> >
> >
> > --
> > 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