Penn White
ecritt1 at alltel.net
Fri Apr 7 14:24:53 CDT 2006
Brilliant! That is a great solution. Should have thought of it myself but I didn't. Maybe next time. Thank you very much. Penn Note: I discovered that you have to be sure to open the form in dialog mode. Setting the form to popup +/- mofal doesn't stop the script and runs the after update event before the user has a chance to select the new Class Section. In the acDialogmode, you don't have to set the Popup & Modal properties to Yes because the acDialog mode does it for you. Thanks again! ----- Original Message ----- From: "Mike & Doris Manning" <mikedorism at verizon.net> To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Sent: Friday, April 07, 2006 11:56 AM Subject: Re: [AccessD] How to force an after update event in another form? > If you are going that route, don't put it in the pop-up's code. Put it in > the procedure that called the pop-up so it will run when the pop-up > closes. > > The only way you could call it from the pop-up is if you changed the after > update event in the main form from private to public. > > Doris Manning > mikedorism at verizon.net > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com