April 15th, 2005, 02:10 PM
Difference between Module and Class Module
I am going to add threading to my program and have been reading and studying this post http://www.codeguru.com/forum/showth...ultiple+thread . I have my program complete, but the functions I want to use for threading are in a Module, and in the example the threaded function is in a Class Module. Can I just copy my code from the Module to a Class Module without any problems? As far as I can tell the two aren't any different code wise.. ?
April 15th, 2005, 02:41 PM
Re: Difference between Module and Class Module
Something about Forms/Modules and Class Modules..
Code in Visual Basic is stored in modules. There are three kinds of modules: form, standard, and class.
Simple applications can consist of just a single form, and all of the code in the application resides in that form module. As your applications get larger and more sophisticated, you add additional forms. Eventually you might find that there is common code you want to execute in several forms. You don't want to duplicate the code in both forms, so you create a separate module containing a procedure that implements the common code. This separate module should be a standard module. Over time, you can build up a library of modules containing shared procedures.
Each standard, class, and form module can contain:
- Declarations. You can place constant, type, variable, and dynamic-link library (DLL) procedure declarations at the module level of form, class or standard modules.
- Procedures. A Sub, Function, or Property procedure contains pieces of code that can be executed as a unit. These are discussed in the section "Procedures" later in this chapter.
Form modules (.FRM file name extension) are the foundation of most Visual Basic applications. They can contain procedures that handle events, general procedures, and form-level declarations of variables, constants, types, and external procedures. If you were to look at a form module in a text editor, you would also see descriptions of the form and its controls, including their property settings. The code that you write in a form module is specific to the particular application to which the form belongs; it might also reference other forms or objects within that application.
Standard modules (.BAS file name extension) are containers for procedures and declarations commonly accessed by other modules within the application. They can contain global (available to the whole application) or module-level declarations of variables, constants, types, external procedures, and global procedures. The code that you write in a standard module isn't necessarily tied to a particular application; if you're careful not to reference forms or controls by name, a standard module can be reused in many different applications.
Class modules (.CLS file name extension) are the foundation of object-oriented programming in Visual Basic. You can write code in class modules to create new objects. These new objects can include your own customized properties and methods. Actually, forms are just class modules that can have controls placed on them and can display form windows.
Click Here to Expand Forum to Full Width