Gustav at cactus.dk
Wed Jul 18 03:16:52 CDT 2007
Hi Borge Yes, setting Me.Dirty is preferable. It tells the form to save the current record, while DoCmd.RunCommand tells the application to tell the active form to save its current record. /gustav >>> pcs at azizaz.com 18-07-2007 00:03 >>> Gustav, Never knew that doing a me.dirty = false actually saves the record on the Form I mentioned in my first email that I would save the record on the form with a docmd.save. What I meant was : docmd.runcommand accmdsaverecord Is a me.dirty = false preferable to a docmd.runcommand accmdsaverecord ? regards borge ----- Original Message ----- From: "Gustav Brock" <Gustav at cactus.dk> To: <accessd at databaseadvisors.com> Sent: Tuesday, July 17, 2007 12:17 AM Subject: Re: [AccessD] Lock of Record - Memofields Hi Borge It tells the form to save the record using the method of the form for this purpose. More precisely, it should look: If Me.Dirty = True Then ' The record has been edited. ' Save the record. Me.Dirty = False End If I'm not saying this is the magic cure. However, DoCmd operations may not always work as expected under stress, and it may be a stress situation when you - at the same time - wish to save a record and move to the next. /gustav >>> pcs at azizaz.com 16-07-2007 15:35 >>> Hi Gustav, I don't get it .... please explain what the me.dirty = false can do in this context. ... also, I admit I didn't get David's method either... borge ----- Original Message ----- From: "Gustav Brock" <Gustav at cactus.dk> To: <accessd at databaseadvisors.com> Sent: Monday, July 16, 2007 7:41 PM Subject: Re: [AccessD] Lock of Record - Memofields Hi Borge Perhaps you should avoid the indirect DoCmd.Save in favour of the method of the form itself: Me.Dirty = False Also, as David mentions, and as your memos seem so tightly formatted that they should be put in a subtable, you could either do this - or use the method of David. /gustav >>> pcs at azizaz.com 16-07-2007 04:06 >>> Hi, I have a problem with record locking and would like some comments on this. This might be a bit of a long winded explanation so bear with me....
More information about the AccessD mailing list