Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Wed Mar 5 11:35:00 CST 2003
Chris, John, Lambert: Got it. Thank you. Normally, when I call a procedure I use 'Call'. You don't need it but it makes the code more self documenting. In this case however, Access did not like the 'Call' in front of the 'Forms!frmManageMultipleAssets.cmdAdd_Click' Rocky ----- Original Message ----- From: "Chris Mackin" <chris at denverdb.com> To: <accessd at databaseadvisors.com> Sent: Wednesday, March 05, 2003 9:13 AM Subject: RE: [AccessD] Syntax to Call a procedure from another form > You need a Public sub if it's called from another form, and then the syntax > is just: > > Forms!frmName.SubName > > Chris Mackin > Denver Database Consulting, LLC > www.denverdb.com > > > -----Original Message----- > From: accessd-admin at databaseadvisors.com > [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Rocky Smolin - Beach > Access Software > Sent: Wednesday, March 05, 2003 10:04 AM > To: AccessD at databaseadvisors.com > Subject: [AccessD] Syntax to Call a procedure from another form > > > Dear List: > > I always have trouble with this syntax: I want to execute or call a Private > Sub in one form (which is open) from a pop up form. Can' remember the > syntax. Anybody know offhand? > > MTIA > > Rocky Smolin > Beach Access Software > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >