Hi all,
  I've seen a number of code samples where the developer puts the
majority of their code into a regular code module and then have their
UserControl (Form, Class) call into that module.  
  Does anyone know if there is there any benefit to programming this
way?  I haven't seen any documentation indicating pro/cons for it.
Currently I am putting all the code into its related UserControl.
  Is there some memory/performance issue around this?

TIA!

--
Chris

Christopher an obvious benefit is the ability to create reusable code
components.
An example of this is input validation.  You can create one common module
and call the common code from the particular controls.  This results in a
smaller
application size and reusable code components.

Also, although controls can be instantiated multiple times, modules don't.
Therefore, you can place many instances of the same control (or controls
from the same .OCX) that all rely on the same set of routines (instead of
separate instances).

Just my two bits.
--
R. Aaron Zupancic
MCT Visual Basic, Access

http://home.utah-inter.net/azupancic

Hi Aaron:

Doug.

Typically, you are correct. One should try to incapsulate as much as
possible.
However, there are two advanatages to using std code modules.

1) Should you require global data, you can only put it in a std code module.
This allows you, for example, to have many controls access the same database
connection.
In essence, this is a common way to have data exposed which is "sharable" by
multiple instances of classes or controls.

2) This also gives you a convenient way to handle callback functions. The
AddressOf operator will only work with functions specified in std code
modules. This is kind of a safety-net since the address of global functions
don't change as long as the DLL's image is valid.

-Rob

I had the same question, but I would like to know more specifically about
performance issues. Would I incur a big performance loss in using
UserControls instead of classes?

--
****************************************************************************
Mohammed AlQuraishi
SiteBuilder Level 2
ClubIE Team 4
Independent Microsoft Beta Tester
TechWeb/Microsoft 2nd Place ActiveX Contest Winner (Business)
http://www.advancednetsolutions.com

"It is the bias of our society that creates the smart and the stupid." a
*Smart* guy.
"To war is not only to win, it's also to fight."
****************************************************************************

Mohammed

Yours is rather a different question. There's no comparison between
OCX's and classes. You write an OCX if you want something to act as a
control at design time. Classes are a way of designing code.

There are performance issues with any approach. Classes are inclined to
perform slightly less well than 'conventional' code but make it vastly
more maintainable (if designed correctly).

Regards
{*filter*}