referencing form fields in modules

[joemeshuggah]

i am trying to learn vba programming on my own...one of the books i have been reading has a brief section on coupling and cohesion...coupling being too putting too many tasks in one procedure. this is exactly what i have been doing in my first attempts at coding. i have a beforeupdate procedure on a form that has become a confusing mess of checks and balances that interfere with one another.

my thought was to create a module for each procedure, and then just do a series of calls in the beforeupdate of the form to make things easier to sort out and test. the only problem is, i cant seem to get the modules to reference the information on the form (e.g. me.MyField is not recognized). is this possible?

 

[Trevor G]

If creating in a Module that is not behind the form you have to refer to the Form Name as well as the control, the word me wont work in the module, but works behind the form modules.

 

[HiTechCoach]

If ther validation called in the beforeupdate is used be multioepl forms rthen it makes sense to put it in a code module. This allows the code to be easily shared between objects.

If the validation called in the beforeupdate is specific to this form then I would not use a separate code module. I would inset procedures in the form's module. This is also called code behind the form.

FWIW:
Most form validation is very specific to that form and it's objects. To me it do not make sense to place that code in a separate module. Using a separate module adds additional overhead.