Anybody have any opinions about this either way? Any code samples that calls
a module procedure from an event in a form?

Thanx

Leah

--
-------------------------
| gHaD (Aaron Robinson) |
|MJM-PC Solutions, Inc. |
|      Chicago, IL      |
-------------------------

I avoid code behind forms as much as I can because it is real hard to
maintain.  You can put just about everything into standard modules and call
it from from the form.  If you are working with form controls you can even
use a parameter that references the control and pass it with Me!ControlName.

Matthew MacFarland

example: after update , onchange etc....

just so you know , once you set up a specific sub that performs something ,
you can call it anywhere in the form again by just specifing it .

See the example below.
The commandbutton CheckValues is issued after clicking the button , and i
called it also after the update of field NewValue
Thus , by chnaging the CheckValues , all checks everywhere in the form will
be updated

seeyas Steve

example :

Private Sub CheckValues_Click()
dim bla bla
if bla bla then
bla bla bla
else
bla bla
end Sub
-------------------------------------
Private Sub NewValue_AfterUpdate()
CheckValues_Click
end sub

I use form class modules for items that are specific actions on that form,
otherwise, I call a script from standard modules to do the work,
particularly, printing issues and functions.  True, sometimes, I can't
remember whether I have the routine in the forms module or standard module,
but it is easy enough to answer.