Modules

[KenHigg]

Couple more quick questions regarding modules...

1. What are your general guidelines for putting stuff in separate modules. For example I look at portabilty first in case I want to use some code in other databases I'll put chunks of code in their own module. That's the main thing I look at but it seems there should be programabilty issues to consider...?

2. I was looking through an older MS Access book and they suggested qualifying functions and subroutine calls. For example if you have a sub named 'mysubOne' in a module called 'mod1', you should call it twith something like:

call mod1.mysubOne

instead of just:

call mysubOne


Pro's / con's? I suppose it does make it a little more readable - ?

ken

 

[mhartman]

Hello

My take would be to use the full line of code to call a method or sub-routine.

This business about the shortcut way of specifying things is bad programming form. I think Microsoft made an error of letting folks do this.

Regards
Mark

 

[KenHigg]

Hum... I think I agree with you. Plus, isn't there an issue somehow with duplicate subroutine names across modules. I'd hate to think I'd need to remember all of the sub-routine names of the utility type modules I copied from database to database...

ken