[AccessD] Write Conflict - solved

David & Joanne Gould dajomigo at tpg.com.au
Mon Jan 9 00:51:00 CST 2006


Thanks to everyone who offered suggestions. I finally solved the problem. I 
had been focusing on the original form. The problem was actually in the 
other form. I had bound the form back to its table and then updated the 
records through code. The solution was to make the form unbound and 
populate the details from the summoning form.

David

At 01:55 PM 3/01/2006, you wrote:
>Mark
>
>No, I'm just using Access XP keeping the database in Access 2000 format.  I
>think the problem is that the data in the table is updated in the other
>form and therefore doesn't match the subform. I originally wasn't saving
>the changes in the update form but was getting the same problem except that
>the Save button didn't fix things then. So I think I'm closer to the right
>solution except I can't figure out how to do the Save at the right time. It
>seems to be somewhere between when the Close command is activated and
>anything else happening.
>
>Hope this helps.
>
>TIA
>
>David
>
>At 12:41 PM 3/01/2006, you wrote:
> >David -
> >Are you using SQL Server as the backend to your form's data?  I've seen
> >this in the past when SQL tables are being updated.
> >If so, adding a timestamp datatype column to the table seemed to fix it
> >for me.
> >
> >
> >Mark Boyd
> >Senior Consultant
> >Enterprise Risk Services
> >Deloitte & Touche LLP
> >
> >Tel: +1 215 405 5576
> >mboyd at deloitte.com
> >www.deloitte.com
> >
> >
> >-----Original Message-----
> >From: accessd-bounces at databaseadvisors.com
> >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David &
> >Joanne Gould
> >Sent: Saturday, December 31, 2005 8:02 AM
> >To: Access Developers discussion and problem solving
> >Subject: Re: [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
> >
> >
> >--
> >AccessD mailing list
> >AccessD at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/accessd
> >Website: http://www.databaseadvisors.com
> >
> >
> >This message (including any attachments) contains confidential information
> >intended for a specific individual and purpose, and is protected by
> >law.  If you are not the intended recipient, you should delete this message.
> >
> >
> >Any disclosure, copying, or distribution of this message, or the taking of
> >any action based on it, is strictly prohibited. [v.E.1]
> >--
> >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





More information about the AccessD mailing list