Andy Lacey
andy at minstersystems.co.uk
Thu Oct 27 12:59:02 CDT 2005
I reckon he should think in terms of the dialog form's OnOpen pulling values from the calling form rather than the calling form populating the dialog. -- Andy Lacey http://www.minstersystems.co.uk > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > Rocky Smolin - Beach Access Software > Sent: 27 October 2005 16:46 > To: AccessD at databaseadvisors.com > Subject: [AccessD] Fw: Access Question: Modal Form Question > > > Dear List: > > This is from a friend. Any ideas on this? > > MTIA, > > Rocky Smolin > Beach Access Software > http://www.e-z-mrp.com > 858-259-4334 > > ----- Original Message ----- > From: "Mike Dwyer" <mike at aesadvantage.net> > To:Sent: Wednesday, October 26, 2005 6:49 PM > Subject: Access Question: Modal Form Question > > > Ok, I know this has been discussed before so here goes again... > > 1. I have a form that must be opened as a dialog box. > 2. This form is called from one or more VB procedures. > 3. Before this form goes "Modal" I need to change some > values on this form from my VB procedures. > > 4. While this form is "Modal", all other code must be suspended. > > My catch 22 is that I need to manipulate this Modal form to > change values on it but opening this form as DIALOG causes > all code to stop. Opening this form regularly, setting my > values, and then setting the form's Modal property doesn't > stop my other code from executing. > > Anybody got a solution? > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > >