Code Manager (CM) was designed to be a librarian for 
Visual Basic Routines. During my career as a
VB programmer, I found myself hunting for routines
I had already written.

Code Manager consolidates selected routines in one place,
providing maximum resuability.

Code Manager is provided as shareware.


SETUP
-----------------------------
The setup program will install the following files
in the indicated directories. The setup program 
will NOT overwrite newer system files.

NOTE
-----------------------------
The files in the Windows\System directory may be 
required by other programs!!!!!!!!

Use discretion when deleting them!!!!!!!!
-----------------------------
SUPPLIED	Suggested
FILES		Directory
-----------------------------
CODEMGR.EXE	\CODEMGR
CODEMGR.MDB	\CODEMGR
CODEMGR.INI	\WINDOWS
README.TXT	\CODEMGR
VBDB300.DLL	C:\WINDOWS\SYSTEM
MSAES110.DLL	C:\WINDOWS\SYSTEM
MSAJT110.DLL	C:\WINDOWS\SYSTEM
-----------------------------


USAGE
-----------------------------
You must enter the routines into CM before use. A future release
will automatically list, locate and insert existing
code from any .BAS or .FRM file for you (if it's saved as text).

1. Select the "NEW" button
2. Enter the routines name.
3. Enter a description of the routine.
4. Enter the code for the routine.
	Make sure to wrap the code with 
	SUB/END SUB or FUNCTION/END FUNCTION
	statements

If you wish, you may use the clipboard to enter the 
required information from existing code 
(that's what it's all about, right?). 
When the required data has been
entered, press the "OK" button and the entry is automatically saved.

When CM starts, it will fill a listbox of available
routines. Clicking on an entry in the listbox will
display the routines' associated description and code.

Both the description and code may be edited and saved. 

Pressing the "CUT" button will copy the routines' name,
description and code to the clipboard.

To insert the code into your application:

1. Make sure that you are in the declarations 
	section of the form
2. Paste the clipboard contents into the application.
	The description and any variable definitions will stay in
	the declarations section and the code will be separated by
	Visual Basic.
-----------------------------