     |*********************************************************|
     |                                                         |
     |   **********( GEVIRA TECHNOLOGIES GROUP )*********      |
     |             (C) 2001 All Rights Reserved                |
     |                                                         |
     |-------============  U T I L I T Y  ============---------|
     |                                                         |
     |        *********( MGeorge@gevira.com )*********         |
     |          *******( www.gevira.com )********              |
     |                                                         |
     |        SPBuilder Developed by Mathew George             |
     |                                                         |
     |                  New Jersey - U.S.A                     |
     |*********************************************************|


ReadMe for Stored Procedure Builder (SP Builder) v 1.0.0
========================================================

SPBuilder saves immense time by automating the process of building stored procedures
for MS SQL Server. SPBuilder supports the creation of 4 types of Stored Procedures:
1) Insert Stored Procedure
2) Update Stored Procedure
3) Delete Stored Procedure 
4) Insert And Update Stored Procedure

Enhancement Notes:--

Usage:
-----
Using SPBuilder is very easy. Run the application. Enter necessary connection parameters
to connect to your SQL Server database. This brings up the main window of SPBuilder.
To start, enter the name of a Table and then click on the type of Stored Procedure you
want to Build. If the table name is valid, SPBuilder displays all column names along with
type information in the grid. The next step is to choose a Parameter type for each column.

The parameter type for each operation is explained below:

INSERT STORED PROCEDURE:
Insert does not require you to choose any parameter type, but you can optionally choose 
the following 2:
PK+AUTO: This indicates that the selected column is automatically updated (either using Triggers
         or Identity columns). SPBuilder will not use this column in the insert stored procedure.
Ignore:  SPBuilder will not use this column in the stored procedure.

UPDATE STORED PROCEDURE:
Update requires that atleast one column should be selected as Key column:
PK:     This indicates that the selected column is the key column. SPBuilder will add this column as
        an input parameter and will not use this column in the stored procedure.
Ignore: SPBuilder will not use this column in the stored procedure.

DELETE STORED PROCEDURE:
Delete requires that atleast one column should be selected as Key column:
PK: This indicates that the selected column is the key column. SPBuilder will add this column as
    an input parameter and will use this as the Key for delete in the stored procedure.

INSERT AND UPDATE STORED PROCEDURE:
Insert_Update requires that atleast one column should be selected as Key column:
PK+AUTO: This indicates that the selected column is automatically updated (either using Triggers
         or Identity columns). SPBuilder will not use this column in the insert stored procedure.
PK:      This indicates that the following column is used as a key in the Update procedure. It's added
         to the parameter list and is not used in the update columns.
Ignore:  SPBuilder will not use this column in the stored procedure.


Once you have set the parameter type, click on Build SP button and Voila - Well documented, error free
Stored Procedure is generated in the Text Box. You can then copy it to SQL Server.


Installation, File Names and Other Requirements: 
------------------------------------------------
SPBuilder can be installed by executing SPBuilderI.exe. This will create 2 files in the selected
destination folder (SPBuilder.Exe & SPReadMe.txt). Run SPBuilder by executing SPBuilder.Exe.

SPBuilder requires VB 6.0 runtime DLL and Microsoft Flex Grid Component (MSHFLXGD.OCX - SP4+) to
be installed on your machine.

SPBuilder can be uninstalled by deleting both files in the SPBuilder folder.



*************************************************SOFTWARE DISCLAIMER*******************************************
THE SOFTWARE AND THE ACCOMPANYING FILES ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT 
PERMITTED BY APPLICABLE LAW, AUTHOR DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 
ANY IMPLIED WARRANTIES OF PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. 
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 
CONSEQUENTIAL OR INCIDENTAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS 
INTERRUPTION OR LOSS OF BUSINESS INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF 
THE AUTHOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

******************************************************************************************************************


