Using ADO and Stored Procedures _ Visual Basic 6 (VB6)

Using ADO and stored procedures | Visual Basic 6 (VB6)

10-03-2011 22:09:21http://www.vb6.us/tutorials/using-ado-and-stored-procedures-vb6

Search

Level:Top 10 Database Hacks www.Imperva.com/

DatabaseSecurity

Learn to to spot - and stop - them Downloadthis free guide now!NAV Business Intelligence precision-point.com/NAV_bi

SQL Data Warehouse & OLAP cube. FastInstall. Full Integration

Basic Central basiccentral.net

Fresh Visual Basic community From beginnerto expert

VbaDiff www.Technicana.com

Compare VBA code in workbooks quickly andeasily with VbaDiff.

Home › Tutorials

Using ADO and stored procedures

I've modified this some, but the original was by

TheVBProgramer.

Stored Procedures in General

This Visual Basic tutorial is designed to help you understand how

ADO works and how you can use this in conjunction with stored

procedures. Before we jump into the tutorial you need to

understand what stored procedures are. Stored procedures are

programs consisting of SQL statements as well as logic to

control the flow of processing. They can contain both input and

output parameters and can return values. A stored procedure is

called this way because it is stored in the database rather than

the program. It can then be executed by calling it directly from

a client program (such as a VB6 program). Compared to the use

of "in-line" SQL statements that have been used in the other

sample applications, the use of stored procedures offer a couple of advantages:

With stored procedures, there are less SQL statements to be transmitted across the network â€“ only the name of the

stored procedure and any parameters it may require need to be sent over the wire. Not the entire SQL statement.

Stored procedures are parsed and optimized when they are created. They are compiled in the database when created

and remain a part of the database. This is in contrast to the use of in-line SQL statements in your program, which must

be parsed and compiled by the DBMS every time the program is run.

Stored procedures can be used to execute routine data functions such as selecting, inserting, updating, and deleting

data; they can also be used to perform any number of database functions such as backing up the database and

transaction logging.

In this tutorial we will look at some very simple stored procedures using examples in Microsoft Access, SQL Server, and

Oracle. For each, we will look at a sample VB6 application that uses ADO to execute these stored procedures. (Note: You

will need to have access to SQL Server and Oracle in order to run the respective examples using those database systems,

but only Microsoft Access for the other one)

All three versions of the sample application presented here perform identically to the "Customer Table Maintenance"

application presented in the preceding topic.

Stored Procedures in Microsoft Access

MS-Access does not support stored procedures per se, however, saved Query objects can be used. TheADO syntax used to work with Access Query objects is the same syntax used to work with storedprocedures in the high-end databases. Compared to high-end database stored procedures, Access queries

Ads byGoogle

SQL Database Database Code VB6 SQL Server

Visual Basic 6 (VB6)



are quite limited. As mentioned above, stored procedures in high-end databases like SQL Server or Oraclecan contain multiple SQL statements, logic statements to control processing flow, return values, etc. â€“however, with Access queries, you can have only ONE SQL statement â€“ period. The only other languageelement that can be present in an Access query is a set of parameters - queries that have this are referredto as "parameterized queries".For each of the stored procedure sample applications, we will use the equivalent of the "Customer"database that was used in the previous topic on ADO. As you may recall , the Customer database consistsof one table, called Customer, defined as follows in MS-Access:

Column Name Data TypeCustID Number (Long Integer)

LastName Text (50)

FirstName Text (50)

Address Text (50)

City Text (25)State Text (2)

Zip Text (5)

PhoneNumber Text (10)

In the copy of the Cust .mdb MS-Access database used for this sample application, the following Queryobjects were created: SelectCustomer

SELECT FirstName, LastName, Address, City, State, Zip, PhoneNumber, CustIDFROM CustomerORDER BY LastName, FirstName;

InsertCustomerPARAMETERS pCustID Long, pFName Text(50), pLName Text(50), pAddr Text(50),pCity Text(25), pState Text(2), pZip Text(5), pPhone Text(10);INSERT INTO Customer( CustID, FirstName, LastName, Address, City, State, Zip,PhoneNumber )VALUES (pCustID, pFName, pLName, pAddr, pCity, pState, pZip, pPhone);

UpdateCustomerPARAMETERS pCustID Long, pFName Text(50), pLName Text(50), pAddr Text(50),pCity Text(25), pState Text(2), pZip Text(5), pPhone Text(10);UPDATE Customer SET FirstName = pFName, LastName = pLName, Address = pAddr,City = pCity, State = pState, Zip = pZip, PhoneNumber = pPhoneWHERE CustID=pCustID;

DeleteCustomerPARAMETERS pCustID Long;DELETE *FROM CustomerWHERE CustID=pCustID;



Note that the InsertCustomer, UpdateCustomer, and DeleteCustomer queries have a PARAMETERSstatement that precedes the actual SQL statement. The PARAMETERS statement begins with the keywordPARAMETERS followed by one or more pairs of variable name and datatype. Multiple pairs of variablename / datatype are comma separated. The PARAMETERS statement ends with a semicolon. Theparameter variables are then used as values in the body of the SQL statement that follows. Highlights of the code, as it relates to ADO syntax to handle stored procedures as well as how it comparesto the application presented in the preceding topic (where "in-line" SQL was used), are presented below.

As is in the preceding sample app, three ADO object variables (representing and ADO Connection,Command, and Recordset, respectively) are declared at the form level:

Private mobjConn As ADODB.Connection

Private mobjCmd As ADODB.Command

Private mobjRst As ADODB.Recordset

The "ConnectToDB" Sub is nearly identical to that of the preceding sample application . TheConnection object variable is instantiated, its ConnectionString property is set up to specify a DSN-less connection, and the connection is then opened. The Command object variable is theninstatiated, and its ActiveConnection property is set to reference the connection that was justopened. The only difference between this Sub and that of the preceding sample application is thatthe Command object's CommandType is not set here â€“ this is because in the preceding sampleapplication, the CommandType was always a textual string, so we could set CommandType toadCmdText just once and "forget about it". In this application, however, we will use both adCmdTextand adCmdStoredProc, so we will set the CommandType property before each use of theCommand object throughout the application . '-----------------------------------------------------------------------------

Private Sub ConnectToDB()

'-----------------------------------------------------------------------------

Set mobjConn = New ADODB.Connection

mobjConn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" _

& "Data Source=" _

& GetAppPath _

& "Cust.mdb"

mobjConn.Open

Set mobjCmd = New ADODB.Command

Set mobjCmd.ActiveConnection = mobjConn

End Sub

In the "LoadCustomerListView" Sub, the contents of the Customer table is loaded into the listview. Incontrast to the preceding application (which built an in-line SQL statement using a variable whichwas then assigned to the CommandText property of the Command object), this application first setsthe CommandType property of the Command object to adCmdStoredProc, then sets theCommandText property to "SelectCustomer", the name of the stored procedure to execute. Since



the SelectCustomer procedure contains a SELECT statement, the procedure returns a recordset tothe caller â€“ so the recordset returned by the Execute method of the Command object is assignedto the Recordset object variable mobjRst. Note that prior to using the Command object variablemobjCmd, the programmer-defined procedure "ClearCommandParameters" is called. The purposeof this is described a little later below. '-----------------------------------------------------------------------------

Private Sub LoadCustomerListView()

'-----------------------------------------------------------------------------

Dim objCurrLI As ListItem

Dim strZip As String

Dim strPhone As String

ClearCommandParameters

mobjCmd.CommandType = adCmdStoredProc

mobjCmd.CommandText = "SelectCustomer"

Set mobjRst = mobjCmd.Execute

lvwCustomer.ListItems.Clear

With mobjRst

Do Until .EOF

strPhone = !PhoneNumber & ""

If Len(strPhone) > 0 Then

strPhone = "(" & Left$(strPhone, 3) & ") " _

& Mid$(strPhone, 4, 3) & "-" _

& Right$(strPhone, 4)

End If

Set objCurrLI = lvwCustomer.ListItems.Add(, , !FirstName & "", , "Custs")

objCurrLI.SubItems(mlngCUST_LAST_IDX) = !LastName & ""

objCurrLI.SubItems(mlngCUST_ADDR_IDX) = !Address & ""

objCurrLI.SubItems(mlngCUST_CITY_IDX) = !City & ""

objCurrLI.SubItems(mlngCUST_ST_IDX) = !State & ""

objCurrLI.SubItems(mlngCUST_ZIP_IDX) = !Zip & ""

objCurrLI.SubItems(mlngCUST_PHONE_IDX) = strPhone

objCurrLI.SubItems(mlngCUST_ID_IDX) = CStr(!CustID)

.MoveNext

Loop

End With

With lvwCustomer

If .ListItems.Count > 0 Then

Set .SelectedItem = .ListItems(1)

lvwCustomer_ItemClick .SelectedItem

End If

End With

Set objCurrLI = Nothing

Set mobjRst = Nothing

End Sub



The "ClearCommandParameters" Sub is called prior to each use of the Command object. Thisroutine clears the Parameters collection of the Command object. The Parameters collection is usedto specify the parameters that are to be passed to the stored procedure that will be called. (It wasnot necessary to use the Parameters collection to call the SelectCustomer procedure shown abovebecause the SelectCustomer procedure does not have parameters.) Anyway, since we havedeclared the mobjCmd object at the form level, this same object is reused over and over again, sowe must clear any existing Parameters collection from it prior to each use.

'------------------------------------------------------------------------

Private Sub ClearCommandParameters()

'------------------------------------------------------------------------

Dim lngX As Long

For lngX = (mobjCmd.Parameters.Count - 1) To 0 Step -1

mobjCmd.Parameters.Delete lngX

Next

End Sub

In the "cmdSave_Click" event procedure, the code that checks to see whether an add or update hasbeen initiated (among other things) sets the string variable strSPName to "InsertCustomer" or"UpdateCustomer" accordingly . After the "If" statement , the "ClearCommandParameters" Sub iscalled to clear any existing parameters in the Parameters collection, the Command object'sCommandType is set to adCmdStoredProc, the Parameters collection is built (explained in moredetail below), the CommandText property is set to strSPName (which we set above to hold thename of the stored procedure to call), then the Execute method is called to run the procedure. Theprocess can be coded this way because although the InsertCustomer and UpdateCustomerprocedures do different things, they take the exact same set of parameters (this is true only for theAccess example presented in this article).

To build the Parameters collection of the Command object, we use two methods on top of each other. TheCreateParameter method of the Command object specifies the details of the parameter to bepassed to the stored procedure. The resulting parameter object that is created must then be addedto the Parameters collection via the Append method of the Parameters collection of the Commandobject.

The syntax of the CreateParameter method is as follows:

Set parameter = command .CreateParameter(Name, Type, Direction, Size, Value ) where parameter is an ADO Parameter object, command is an ADO Command object, and thearguments are described in the table below:

Argument DescriptionName An optional string representing the name of the Parameter object. If given,

this name is the "ADO name" that is used to represent the Parameter object



in the client-side (e.g. VB) program â€“ it can be â€“ be need not be â€“ thesame name as the actual parameter in the server-side stored procedure.

Type An optional Long value specifying the data type of the Parameter object. Thisvalue is usually specified by an ADO constant. There are well over 30 possiblevalues for the data type. The examples presented in this topic use two ofthese: adInteger (a four-byte integer equivalent to a VB or Access Longdatatype) and adVarChar (a variable-length character field equivalent to a VBString or Access Text datatype). Other possible values include adDate (date/time datatype), adSingle (single-precision floating point datatype), andadDouble (double-precision floating point datatype).

Direction An optional Long value specifying the type of Parameter object. This value isusually specified by an ADO constant. The possible values are:

adParamInput â€“ indicates an input parameter (Note: This is onlydirection supported by Access parameterized queries).

adParamOuput â€“ indicates an output parameter

adParamInputOutput â€“ indicates a two-way parameter

adParamReturnValue â€“ indicates a return valueSize An optional Long value specifying the maximum length for the parameter

value in characters or bytes. Required for text (string) datatypes.Value An optional variant value specifying the value for the Parameter object

(specified for adParamInput and adParamInputOutput parameters).

The ADO Parameter object that is created by the CreateParameter method is not automaticallyappended to the Parameters collection of the Command object, where it ultimately needs to be. Thisallows additional properties of the Parameter object to be set, if needed (in the sample applicationspresented here, we do not need to set additional properties). So to append the newly createdParameter object to the Parameters collection of the Command object, the following syntax is used: command .Parameters.Append parameter

where parameter is an ADO Parameter object, command is an ADO Command object In the sample application, we are taking a "shortcut" by using CreateParameter andParameters.Append in one statement . For example, we are using statements like: mobjCmd.Parameters.Append mobjCmd.CreateParameter("pFName", adVarChar , adParamInput, 50,

txtFirst.Text)

The same result could have been accomplished in separate steps, as follows: ' a separate ADO parameter object variable would have to be declared

Dim objParm As ADODB.Parameter

' a pair of statements like the following would be used for each parameter

' to be passed to the stored procedure

Set objParm = mobjCmd.CreateParameter("pFName", adVarChar , adParamInput, 50, txtFirst.Text )

mobjCmd.Parameters.Append objParm



Note that the same logic that dealt with the record ID in the previous topic's sample application isstill in place here. For an add, the new record ID is obtained by calling the programmer-definedfunction GetNextCustID, which is described a little later below. For an update, the record ID of thecurrently selected item in the listview is used in the UPDATE statement to update the record. Ineither case, the contents of the listview is updated approriately to reflect the insert or update. '-----------------------------------------------------------------------------

Private Sub cmdSave_Click()

'-----------------------------------------------------------------------------


Dim objNewListItem As ListItem

Dim lngIDField As Long

Dim strSPName As String

If Not ValidateFormFields Then Exit Sub

strPhone = txtArea.Text & txtPrfx.Text & txtLine.Text

If mstrMaintMode = "ADD" Then

lngIDField = GetNextCustID()

strSPName = "InsertCustomer"

Set objNewListItem = lvwCustomer.ListItems.Add(, , txtFirst.Text, , "Custs")

PopulateListItem objNewListItem

With objNewListItem

.SubItems(mlngCUST_ID_IDX) = CStr(lngIDField)

.EnsureVisible

End With

Set lvwCustomer.SelectedItem = objNewListItem

Set objNewListItem = Nothing

Else

lngIDField = CLng(lvwCustomer.SelectedItem.SubItems(mlngCUST_ID_IDX))

strSPName = "UpdateCustomer"

lvwCustomer.SelectedItem.Text = txtFirst.Text

PopulateListItem lvwCustomer.SelectedItem

End If



mobjCmd.Parameters.Append mobjCmd.CreateParameter("pCustID", adInteger, adParamInput, ,

lngIDField)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pFName", adVarChar , adParamInput, 50,

txtFirst.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pLName", adVarChar , adParamInput, 50,

txtLast.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pAddr", adVarChar , adParamInput, 50,

txtAddr.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pCity", adVarChar , adParamInput, 25,

txtCity.Text)



mobjCmd.Parameters.Append mobjCmd.CreateParameter("pState", adVarChar , adParamInput, 2,

txtState.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pZip ", adVarChar, adParamInput, 5,

txtZip.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pPhone", adVarChar , adParamInput, 10, strPhone)

mobjCmd.CommandText = strSPName

mobjCmd.Execute

SetFormState True

mblnUpdateInProgress = False

End Sub

When we need to add a new record, a new, unique record ID must generated. In this particularsample application , the record ID is defined as a Long Integer in the database. The GetNextCustIDfunction shown below uses the SQL MAX function to find the highest existing value for the CustIDfield, adds one to it, and returns that value to the caller . Note that in this application, the"ClearCommandParameters" sub is called, then the CommandType property of the Command objectis set to adCmdText. The CommandText property is then set to the appropriate SQL string. This isthe only place in the program where in-line SQL is used instead of a stored procedure.

It should be noted that if the CustID field was defined as an Access AutoNumber field, the logic of this

application would have to be modified accordingly. Basically, we want to be able to know what thevalue of the new record ID is and use it after the record has been added to the table. For anAutonumber field, we would have to use the AddNew method of the Recordset and then assign therecord ID field to a variable for later use. In that we wanted to demonstrate the use of SQL INSERTstatements in this and the preceding sample applications, it was decided to not use an Autonumberfield for the record ID.

In the SQL Server and Oracle examples presented later on in this article, the "autonumber" concept IS

applied to the record ID. With the additional capabilities of the stored procedures in those databasesystems, it is possible to retrieve the value of the record ID for a newly inserted record forsubsequent processing. '------------------------------------------------------------------------

Private Function GetNextCustID() As Long

'------------------------------------------------------------------------


mobjCmd.CommandType = adCmdText

mobjCmd.CommandText = "SELECT MAX(CustID) AS MaxID FROM Customer"


If mobjRst.EOF Then

GetNextCustID = 1

ElseIf IsNull(mobjRst!MaxID) Then



GetNextCustID = 1

Else

GetNextCustID = mobjRst!MaxID + 1

End If


End Function

In the "cmdDelete_Click" event procedure, after it has been confirmed that the user truly wants todelete the record, the set of statements to accomplish this via the "DeleteCustomer" storedprocedure is executed. As is done prior to each use of the Command object, the"ClearCommandParameters" Sub is called to clear the Parameters collection of the Commandobject. The CommandType property of the Command object is then set to adCmdStoredProc. Oneparameter (the record ID of the customer record to be deleted) is created and appended to theParameters collection. The name of the stored procedure to be called, "DeleteCustomer", isassigned to the Command object's CommandText property. The Execute method of the Commandobject is then invoked to run the procedure to delete the record from the Customer table. Logic isthen executed to update the listview to remove the deleted record. '-----------------------------------------------------------------------------

Private Sub cmdDelete_Click()

'-----------------------------------------------------------------------------

Dim strFirstName As String

Dim strLastName As String

Dim lngCustID As Long

Dim lngNewSelIndex As Long

If lvwCustomer.SelectedItem Is Nothing Then

MsgBox "No Customer selected to delete.", _

vbExclamation, _

"Delete"

Exit Sub

End If

With lvwCustomer.SelectedItem

strFirstName = .Text

strLastName = .SubItems(mlngCUST_LAST_IDX)

lngCustID = CLng(.SubItems(mlngCUST_ID_IDX))

End With

If MsgBox("Are you sure that you want to delete Customer '" _

& strFirstName & " " & strLastName & "'?", _

vbYesNo + vbQuestion, _

"Confirm Delete") = vbNo Then

Exit Sub

End If






lngCustID )

mobjCmd.CommandText = "DeleteCustomer"

mobjCmd.Execute

With lvwCustomer

If .SelectedItem.Index = .ListItems.Count Then

lngNewSelIndex = .ListItems.Count - 1

Else

lngNewSelIndex = .SelectedItem.Index

End If

.ListItems.Remove .SelectedItem.Index

If .ListItems.Count > 0 Then

Set .SelectedItem = .ListItems(lngNewSelIndex)

lvwCustomer_ItemClick .SelectedItem

Else

ClearCurrRecControls

End If

End With

End Sub

When the program ends, the DisconnectFromDB sub is called to clean up the database objects. TheCommand object variable mobjCmd is set to Nothing. The ADO Connection is then closed byissuing the Close method on the Connection object variable mobjConn, and then that object is set toNothing as well. Note: It was not necessary to "clean up" the Recordset object variable mobjRst,because it was set to Nothing at the end of each Sub in which it was used. '-----------------------------------------------------------------------------

Private Sub DisconnectFromDB()

'-----------------------------------------------------------------------------

Set mobjCmd = Nothing

mobjConn.Close

Set mobjConn = Nothing

End Sub

Download the project files for the Access version of the sample application here.

SQL Server Stored ProceduresNote: In order to run the next sample application , you will need to have access to SQL Server. If you do nothave access to SQL Server, possible options are to find a trial version of SQL Server that Microsoft offersfrom time to time (check Microsoft's website ; you may also find a trial version on a CD that comes with abook on SQL Server). Another alternative is to use the MSDE (Microsoft Data Engine). MSDE is a scaled-down version of SQL Server that Microsoft offers for free as a download from their website . MSDE does



NOT come with the SQL Server front end tools (Enterprise Manager, Query Analyzer, etc.) â€“ although youmay find third-party products that fill that need. For this sample application, SQL Server 2000 was used. A database called CustomerTest was created, andin that database, the Customer table was created using Enterprise Manager. Following is the equivalentCREATE TABLE statement that could have been used to create the Customer table:

CREATE TABLE Customer(CustID int IDENTITY(1, 1) NOT NULL,LastName varchar(50),FirstName varchar(50),Address varchar(50),City varchar(25),State varchar(2),Zip varchar(5),PhoneNumber varchar(10))

Note that the CustID field was defined as an int datatype. In SQL Server, the int datatype is a four-byteinteger (equivalent to a Long in Access). Note also that the IDENTITY attribute was assigned to the CustIDfield. This allows for the automatic population of this field with a unqiue value whenever a Customer recordis inserted into the table. The (1, 1) after IDENTITY instructs SQL Server to start the seed value with 1 andincrement by 1. The remaining fields are defined as varchar, which enables them to store variable lengthtext data up to a maximum length specified by the number in parentheses. In SQL Server, stored procedures are coded in a language called Transact-SQL (or T-SQL for short). Inthe SQL Server user interface, stored procedures are entered via the Enterprise Manager or the QueryAnalyzer; stored procedures may also be entered into a SQL Server database via batch scripts. The generalsyntax structure of a SQL stored procedure (simplified) is:

CREATE PROCEDURE procedurename[(@parameter datatype [OUTPUT] [, ...])] AS statement 1;. . .statement n;

In the syntax above, procedurename represents the name of the stored procedure, which may be up 128characters in length. This is followed by an optional parameter list. If present, the parameters are comma-delimited and enclosed in parentheses. Each parameter consists of a name beginning with an "at" sign (@),followed by its datatype, optionally followed by the keyword OUTPUT (only if it is in fact an output parameterâ€“ otherwise, the parameter is assumed to be input). Following the parameter list (if present) is thekeyword AS. That completes the stored procedure "header". The body of the stored procedure consists ofone or more statements (which may be a mix of SQL queries and T-SQL logic statements); each statementends with a semicolon (;). The following four stored procedures were created for this sample application: SelectCustomer. This is a very basic procedure, consisting of one SQL SELECT statement. When calledfrom the VB program with ADO, a recordset object will be returned.



CREATE PROCEDURE SelectCustomer AS SELECT FirstName, LastName, Address, City, State, Zip, PhoneNumber, CustIDFROM CustomerORDER BY LastName, FirstName;

InsertCustomer. This procedure has an argument list consisting of the values for the data that will beinserted into a new row of the Customer table. Recall that the CustID is defined with the IDENTITYattribute, and as such, must not be specified in the INSERT statement itself â€“ SQL Server will populatethat column automatically. However, we want to know what value was inserted for the CustID. The SQLServer built-in function @@IDENTITY returns the last inserted Identity value. The last statement in theprocedure assigns the value returned by @@IDENTITY to the @pCustID parameter, which is defined asan OUTPUT parameter in the parameter list. In our VB program, we will be able to retrieve this value fromthe corresponding ADO Parameter object. (Note: In T-SQL, a form of the SELECT statement is used forassignment statements.)

CREATE PROCEDURE InsertCustomer( @pCustID int OUTPUT, @pFName varchar(50), @pLName varchar(50), @pAddr varchar(50), @pCity varchar(25), @pState varchar(2), @pZip varchar(5), @pPhone varchar(10))AS INSERT INTO Customer( FirstName, LastName, Address, City, State, Zip, PhoneNumber )VALUES ( @pFName, @pLName, @pAddr, @pCity, @pState



, @pZip, @pPhone); SELECT @pCustID = @@IDENTITY;

UpdateCustomer. This procedure has an argument list consisting of the values for the row of data (basedon the CustID) that will be updated in the Customer table. The body of the procedure consists of a singleUPDATE statement .

CREATE PROCEDURE UpdateCustomer( @pCustID int, @pFName varchar(50), @pLName varchar(50), @pAddr varchar(50), @pCity varchar(25), @pState varchar(2), @pZip varchar(5), @pPhone varchar(10))ASUPDATE CustomerSET FirstName = @pFName,LastName = @pLName,Address = @pAddr,City = @pCity,State = @pState,Zip = @pZip,PhoneNumber = @pPhoneWHERE CustID = @pCustID;

DeleteCustomer. This procedure takes in one parameter â€“ the CustID of the Customer row to bedeleted. The body of the procedure consists of a single DELETE statement.

CREATE PROCEDURE DeleteCustomer(@pCustID int)AS DELETE FROM CustomerWHERE CustID = @pCustID;

Highlights of the SQL Server version of the sample application, as it relates to ADO syntax to handle storedprocedures are presented below.

As is in the preceding sample app, three ADO object variables (representing and ADO Connection,Command, and Recordset, respectively) are declared at the form level:






The "ConnectToDB" Sub is nearly identical to that of the preceding sample application . TheConnection object variable is instantiated, its ConnectionString property is set up to specify a DSN-less connection, and the connection is then opened. The ConnectionString specifies the requiredarguments needed for the SQL Server installation used in the sample application . The requiredarguments and/or values for your SQL Server installation will be different. The Command objectvariable is then instatiated, and its ActiveConnection property is set to reference the connection thatwas just opened.'-----------------------------------------------------------------------------


'-----------------------------------------------------------------------------


mobjConn.ConnectionString = "Driver=SQL Server;" _

& "Server=BRUCE-DESKTOP;" _

& "Database=CustomerTest"

mobjConn.Open



End Sub

The other database routines in this SQL Server version of the application are identical to that of the Accessversion, with the exception of the â€œcmdSave_Clickâ € event procedure as described below:

In the "cmdSave_Click" event procedure, prior to the code that checks to see whether an add orupdate has been initiated, the "ClearCommandParameters" Sub is called to clear any existingparameters in the Parameters collection and the Command object's CommandType is set toadCmdStoredProc. Within the â€œIfâ € structure that checks to see whether an add or update hasbeen initiated, the code on â€œboth sidesâ € builds the Parameters collection, sets theCommandText property to â€œInsertCustomerâ € or â€œUpdateCustomerâ € accordingly, and callsthe Execute method is called to run the appropriate procedure.

The set of Parameters built on both sides is the same, except for the â€œpCustIDâ € parameter (forthe Customer ID). On the â€œADDâ € side, where we are getting ready for an Insert, the directionargument of the CreateParameter method must be specified as adParamOutput because thatparameter was defined as OUTPUT in the stored procedure. Note that after the stored procedure isexecuted, the output parameter is used to populate the Customer ID column of the newly addedListItem in the ListView, corresponding to the newly added record: With objNewListItem

.SubItems(mlngCUST_ID_IDX) = mobjCmd.Parameters("pCustID")

.EnsureVisible

End With



Because of the use of the Identity attribute on the Customer ID field in the Customer table and theuse of the output parameter, the programmer-defined function â€œGetNextCustIDâ € used in theAccess version of the application is not needed. '-----------------------------------------------------------------------------


'-----------------------------------------------------------------------------





strPhone = txtArea.Text & txtPrfx.Text & txtLine.Text



If mstrMaintMode = "ADD" Then

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pCustID", adInteger, adParamOutput)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pFName", adVarChar, adParamInput, 50,

txtFirst.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pLName", adVarChar, adParamInput, 50,

txtLast.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pAddr", adVarChar, adParamInput, 50,

txtAddr.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pCity", adVarChar, adParamInput, 25,

txtCity.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pState", adVarChar, adParamInput, 2,

txtState.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pZip", adVarChar, adParamInput, 5,

txtZip.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pPhone", adVarChar, adParamInput, 10, strPhone)

mobjCmd.CommandText = "InsertCustomer"

mobjCmd.Execute

Set objNewListItem = lvwCustomer.ListItems.Add(, , txtFirst.Text, , "Custs")

PopulateListItem objNewListItem

With objNewListItem

.SubItems(mlngCUST_ID_IDX) = mobjCmd.Parameters("pCustID")

.EnsureVisible

End With

Set lvwCustomer.SelectedItem = objNewListItem

Set objNewListItem = Nothing

Else

lngIDField = CLng(lvwCustomer.SelectedItem.SubItems(mlngCUST_ID_IDX))


lngIDField)



mobjCmd.Parameters.Append mobjCmd.CreateParameter("pFName", adVarChar, adParamInput, 50,

txtFirst.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pLName", adVarChar, adParamInput, 50,

txtLast.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pAddr", adVarChar, adParamInput, 50,

txtAddr.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pCity", adVarChar, adParamInput, 25,

txtCity.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pState", adVarChar, adParamInput, 2,

txtState.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pZip", adVarChar, adParamInput, 5,

txtZip.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pPhone", adVarChar, adParamInput, 10, strPhone)

mobjCmd.CommandText = "UpdateCustomer"

mobjCmd.Execute

lvwCustomer.SelectedItem.Text = txtFirst.Text

PopulateListItem lvwCustomer.SelectedItem

End If

SetFormState True


End Sub

Download the project files for the SQL Server version of the sample application here.

Oracle Stored ProceduresNote: In order to run the next sample application , you will need to have access to Oracle. If you do notalready have access to Oracle, you may be able to download a version for personal use from Oracle'swebsite. Be advised that the download is quite large and may not be feasible without a high-speedconnection. The installation process is lengthy as well. In any event, a visit to their website may beworthwhile to see what is available. Oracle is one of the oldest and most robust relational database products. Unlike SQL Server, which runsonly on Microsoft operating systems, Oracle is cross-platform and runs on UNIX and other systems as wellas Windows. It is not as easy to use as SQL Server, but what it lacks in ease of use, it makes up for inhorsepower; it is well-suited to high-volume transaction processing. As far as a front-end interface isconcerned, Oracle has traditionally offered SQL Plus, which is essentially a command-line interface,although in recent years their GUI-based interfaces have improved. Many folks use third-party interfaceproducts such as Quest SQL Navigator, Toad, or PL/SQL Developer from Allround Automations. For this sample application, Personal Oracle 9i was used. The Customer table was created in the default"SCOTT" schema within the default database. The CREATE TABLE statement is as follows:

CREATE TABLE CUSTOMER(CUSTID NUMBER NOT NULL,LASTNAME VARCHAR2(50),



FIRSTNAME VARCHAR2(50),ADDRESS VARCHAR2(50),CITY VARCHAR2(25),STATE VARCHAR2(2),ZIP VARCHAR2(5),PHONENUMBER VARCHAR2(10))

The CUSTID field was defined a NUMBER datatype, which can hold any numeric value. The remainingfields are defined as VARCHAR2, which enables them to store variable length text data up to a maximumlength specified by the number in parentheses. Although not seen in the CREATE TABLE statementabove, a primary key constraint was placed on the CUSTID field to ensure that its value will always beunique. Oracle does not have an AutoNumber or Identity attribute that can be assigned to individual fields; however,Oracle does provide a SEQUENCE object which can be used to accomplish the same objective. For thisapplication an Oracle sequence object called CUST_ID_SEQ was created. When you create a sequenceobject, you specify a starting value and an increment value. To use the sequence, you refer to its NEXTVALproperty (which will retrieve the next value of the sequence). You can also refer the sequence's CURRVALproperty, which retrieves the current value of the sequence. For example, in the list of values to be insertedinto a new CUSTOMER record, CUST_ID_SEQ.NEXTVAL could be used for the value of the CUSTIDfield. In Oracle, stored procedures are coded in a language called PL/SQL . It is a fairly robust language similarin syntax to Pascal and Ada. The general syntax structure of an Oracle stored procedure (simplified) is:

CREATE [OR REPLACE] PROCEDURE procedurename[(parameter directiondatatype [, ...])] IS[variable_1 datatype;...variable_n datatype;]BEGINstatement 1;. . .statement n;

END procedurename; In the syntax above, procedurename represents the name of the stored procedure. This is followed by anoptional parameter list. If present, the parameters are comma-delimited and enclosed in parentheses. Eachparameter consists of the parameter name, its direction (either IN, OUT, or IN OUT), and its datatype.Following the parameter list (if present) is the keyword IS. If any local variables are required, they aredeclared next (a variable declaration consists of its name followed by its datatype, ending with a semicolon).The body of the stored procedure starts with the keyword BEGIN and consists of one or more statements(which may be a mix of SQL queries and PL/SQL logic statements); each statement ends with a semicolon(;). The procedure ends with the keyword END followed by the procedure name. The following four procedures were created for this application:



SelectCustomer. Returning a recordset from an Oracle stored procedure has traditionally not been asimple matter. However, from Oracle 9i forward as well as ADO 2.5 forward, it is now almost as easy as itis in SQL Server and Access. To return a recordset from an Oracle stored procedure, you must declare anoutput (OUT) parameter of type SYS_REFCURSOR. In the body of the procedure, you code a PL/SQLOPEN statement using the syntax: OPEN ref_cusrsor_parameter_name FOR select_statement; The recordset will be returned to the VB program via the SYS_REFCURSOR parameter . You need NOTcreate an ADO Parameter object to hold the recordset (if there were other parameters used in thisprocedure, you WOULD of course need ADO Parameters for those).

create procedure SelectCustomer(p_recordset out SYS_REFCURSOR) isbeginopen p_recordset forSELECT FirstName, LastName, Address, City, State, Zip, PhoneNumber, CustIDFROM CustomerORDER BY LastName, FirstName; end SelectCustomer;

InsertCustomer. This procedure has an argument list consisting of the values for the data that will beinserted into a new row of the Customer table. The first statement is a special form of the SELECTstatement. The INTO option enables you to select a single value from a table and store it in a localvariable. In this case, the value we want to select is the NEXTVAL property of the CUST_ID_SEQsequence, and the variable we are selecting that into is the pCustID output parameter. In our VB program,we will be able to retrieve this value from the corresponding ADO Parameter object. The table that we areselecting from is DUAL, which is built in "dummy" table in Oracle (used when you have to select from"something" but it doesnâ€™t matter what). The value we set for pCustID, along with the other inputparameters, are then used in the VALUES list of the INSERT statement .

CREATE PROCEDURE InsertCustomer(pCustID out number,pFName in varchar2,pLName in varchar2,pAddr in varchar2,pCity in varchar2,pState in varchar2,pZip in varchar2,pPhone in varchar2)ISBEGIN SELECT CUST_ID_SEQ.NEXTVAL INTO pCustID FROM DUAL; INSERT INTO Customer( CustID, FirstName, LastName, Address, City, State, Zip,PhoneNumber )VALUES ( pCustID, pFName, pLName, pAddr, pCity, pState, pZip, pPhone );



END InsertCustomer;

UpdateCustomer. This procedure has an argument list consisting of the values for the row of data (basedon the CustID) that will be updated in the Customer table. The body of the procedure consists of a singleUPDATE statement .

CREATE PROCEDURE UpdateCustomer(pCustID in number,pFName in varchar2,pLName in varchar2,pAddr in varchar2,pCity in varchar2,pState in varchar2,pZip in varchar2,pPhone in varchar2)ISBEGIN UPDATE CustomerSET FirstName = pFName,LastName = pLName,Address = pAddr,City = pCity,State = pState,Zip = pZip,PhoneNumber = pPhoneWHERE CustID = pCustID; END UpdateCustomer;

DeleteCustomer. This procedure takes in one parameter â€“ the CustID of the Customer row to bedeleted. The body of the procedure consists of a single DELETE statement.

CREATE PROCEDURE DeleteCustomer(pCustID in number)ISBEGINDELETE FROM CustomerWHERE CustID = pCustID; END DeleteCustomer;

The VB code for the Oracle version of the application is identical to the SQL Server version, with the soleexception of the ConnectionString. In the statement below, the ConnectionString specifies the requiredarguments needed for the Oracle installation used in the sample application. The required arguments and/or values for your Oracle installation will be different. mobjConn.ConnectionString = "Provider=MSDAORA.1;" _



& "Data Source=THEVBPRO;" _

& "User ID=scott;" _

& "Password=tiger"

Download the project files for the Oracle version of the sample application here.

Printer Friendly 129605 reads

Wed, 03/09/2011 - 04:35 — Sandipon (not verified)

Comments

runtime error when executing stored procedure in accessdatabase

I created a stored procedure named "CreateUser" in my application 's backend i.e. MS-Access database for creating users of

the VB application in the "Users" table. In the "CreateUser" form, there are 4 objects viz. UserId(TextBox), New Password

(TextBox), Confirm Password(TextBox) and the last one User Group(ComboBox ) from which the user selects the appropriate

group of users to which this new user will belong and have the necessary privileges set. The code for the CreateUser form

(frmUser.frm) is as follows:

Option Explicit




Private mstrMaintMode As String

Private mblnFormActivated As Boolean

Private mblnUpdateInProgress As Boolean

Dim conn As New ADODB.Connection, rec As New ADODB.Recordset

Dim esql As String, esql1 As String



Dim KeyCode As Integer

Dim ComboSelItem As Long

Dim StrSelItem As String

Private Sub CmbUsrGrp_Change()

If CmbUsrGrp.ListIndex <> -1 Then

StrSelItem = CmbUsrGrp.List(CmbUsrGrp.ListIndex)

ComboSelItem = CmbUsrGrp.ItemData(CmbUsrGrp.ListIndex)

End If

End Sub

Private Sub CmbUsrGrp_Keydown(KeyCode As Integer, Shift As Integer)

If KeyCode = KeyCodeConstants.vbKeyReturn Then

cmdSave.SetFocus

End If

End Sub

Private Sub cmdSave_KeyPress(KeyAscii As Integer)

If KeyAscii = KeyCodeConstants .vbKeyReturn Then

Unload Me

End Sub

'*****************************************************************************

'* General Form Events *

'*****************************************************************************

'-----------------------------------------------------------------------------

Private Sub Form_Load()

'-----------------------------------------------------------------------------

CenterForm Me

SetFormState True

ConnectToDB



mobjCmd.CommandText = "SelectUserGroup"


With mobjRst

Do Until .EOF



CmbUsrGrp.AddItem (mobjRst.Fields(1))

CmbUsrGrp.ItemData(CmbUsrGrp.NewIndex) = mobjRst.Fields(0)

.MoveNext

Loop

End With

mobjRst.Close

End Sub

'-----------------------------------------------------------------------------

Private Sub Form_Activate()

'-----------------------------------------------------------------------------

If mblnFormActivated Then Exit Sub

Refresh

SetFormState True

mblnFormActivated = True

End Sub

'-----------------------------------------------------------------------------

Private Sub Form_Unload(Cancel As Integer)

'-----------------------------------------------------------------------------

Dim objRst As ADODB.Recordset

If mblnUpdateInProgress Then

MsgBox "You must save or cancel the current action before " _

& "closing this window.", _

vbInformation, _

"Cannot Close"

Cancel = 1

Exit Sub

End If

DisconnectFromDB

Set frmUser = Nothing

End Sub

'*****************************************************************************

'* Command Button Events *

'*****************************************************************************



'-----------------------------------------------------------------------------

Private Sub cmdClose_Click()

'-----------------------------------------------------------------------------

Unload Me

End Sub

'-----------------------------------------------------------------------------


'-----------------------------------------------------------------------------




Dim strSPName As String

Dim IntUsrGrp As Long


If Not ValidatePasswordMatch Then Exit Sub

If Not ValidateComboField Then Exit Sub

CmbUsrGrp_Change

lngIDField = GetNextUserID()

strSPName = "CreateUser"



mobjCmd.Parameters.Append mobjCmd.CreateParameter("pID", adInteger, adParamInput, , lngIDField)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pUserID", adVarChar, adParamInput, 20, txtUserID.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pPasswd", adVarChar, adParamInput, 10, txtPasswd.Text)

mobjCmd.Parameters.Append mobjCmd.CreateParameter("pUser_GrpId", adInteger, adParamInput, , ComboSelItem)

'On Error GoTo procError

mobjCmd.CommandText = strSPName

mobjCmd.Execute

'procError:

SetFormState True


Unload Me

End Sub



'-----------------------------------------------------------------------------

Private Sub cmdCancel_Click()

'-----------------------------------------------------------------------------

' mblnUpdateInProgress = False

' SetFormState True

' lvwCustomer_ItemClick lvwCustomer.SelectedItem

DisconnectFromDB

SetFormState False

Unload Me

End Sub

'*****************************************************************************

'* Other Control Events *

'*****************************************************************************

'*****************************************************************************

'* Programmer-Defined Subs & Functions *

'*****************************************************************************

'-----------------------------------------------------------------------------


'-----------------------------------------------------------------------------


mobjConn.ConnectionString = "Provider=Microsoft .Jet.OLEDB.4.0;" _

& "Data Source=" _

& GetAppPath _

& "\Database\CMS.mdb"

mobjConn.Open



End Sub

'-----------------------------------------------------------------------------

Private Sub DisconnectFromDB()

'-----------------------------------------------------------------------------

Set mobjCmd = Nothing

mobjConn.Close

Set mobjConn = Nothing

End Sub



'-----------------------------------------------------------------------------

Private Sub ClearCurrRecControls()

'-----------------------------------------------------------------------------

gblnPopulating = True

gblnPopulating = False

End Sub

'-----------------------------------------------------------------------------

Private Sub SetFormState(pblnEnabled As Boolean)

'-----------------------------------------------------------------------------

cmdSave.Enabled = pblnEnabled

cmdCancel.Enabled = pblnEnabled

End Sub

'-----------------------------------------------------------------------------

Private Function ValidateFormFields() As Boolean

'-----------------------------------------------------------------------------

If Not ValidateRequiredField(txtUserID, "User ID") Then

ValidateFormFields = False

Exit Function

End If

If Not ValidateRequiredField(txtPasswd, " New Password") Then


Exit Function

End If

If Not ValidateRequiredField(txtcpass, "Confirm Password") Then


Exit Function

End If

ValidateFormFields = True

End Function

'------------------------------------------------------------------------

Private Function GetNextUserID() As Long

'------------------------------------------------------------------------


mobjCmd.CommandType = adCmdText

mobjCmd.CommandText = "SELECT MAX(ID) AS MaxID FROM Users"




' If mobjRst.EOF Then

' GetNextUserID = 1

If IsNull(mobjRst!MaxID) Then

GetNextUserID = 1

Else

GetNextUserID = mobjRst!MaxID + 1

End If


End Function

'------------------------------------------------------------------------

Private Sub ClearCommandParameters()

'------------------------------------------------------------------------

Dim lngX As Long

For lngX = (mobjCmd.Parameters.Count - 1) To 0 Step -1

mobjCmd.Parameters.Delete lngX

Next

End Sub

Private Sub txtcpass_KeyDown(KeyCode As Integer, Shift As Integer)


CmbUsrGrp.SetFocus

End If

End Sub

Private Sub txtPasswd_KeyDown(KeyCode As Integer, Shift As Integer)


txtcpass.SetFocus

End If

End Sub

'-----------------------------------------------------------------------------

Private Function ValidatePasswordMatch() As Boolean

'-----------------------------------------------------------------------------

If Not ValidatePasswordFieldMatch(txtPasswd, txtcpass) Then

ValidatePasswordMatch = False

Exit Function

End If

ValidatePasswordMatch = True

End Function

Private Sub txtUserID_KeyDown(KeyCode As Integer, Shift As Integer)



Wed, 09/15/2010 - 12:09 — Hosko (not verified)


txtPasswd.SetFocus

End If

End Sub

'-----------------------------------------------------------------------------

Private Function ValidateComboField() As Boolean

'-----------------------------------------------------------------------------

If Not ValidateComboBoxField(CmbUsrGrp, "User Group") Then

ValidateComboField = False

Exit Function

End If

ValidateComboField = True

End Function

However, when I run the application, i got the following run time error :

Run Time error -217......(80040e57): the field is too small to accept the amount of data that is being inserted. Please

insert / append less data.

I could not figure out what might be causing this error. Please help.

Regards,

Sandipon

reply

Excel VBA and Oracle Stored Procedures

I have a few Excel (2003) reports that I created to work off SQL Server and now the back-end is migrating to Oracle...

never having worked with Oracle I've been tearing my hear out trying to do what's pretty simple in the Excel/SQL Server

world.... namely;

1. Create a stored procedure and run it

2. Call that stored procedure from Excel and dump the outcome to a worksheet.

I've been tearing my hear out for days trying to work out how to do this and there's very little on the net that describes

how to do this in a straightforward manor.

I used your VB tutorial as a basis and messed around until it worked in VBA - so thanks. You rock. If you don 't mind, I'm

going to paste a summary of how I did it in here. Kind of a karmic "give back" to the world since I rely heavily on useful

info on the net for my professional existance. Hopefully it 'll help someone else.

-----------------------------------------

Creating the Oracle SPROC (using Oracle SQL Developer)

--This creates a SPROC that takes in 1 parameter, uses that in the SQL WHERE clause and then outputs the results to an

'out' sys_refcursor



--parameter. Remove the input parameter if you don 't need it.

-----------------------------------------

create or replace

PROCEDURE TESTPROC

(

ROW_NUM IN NUMBER

, P_RECORDSET OUT SYS_REFCURSOR

) AS

BEGIN

open p_recordset for

Select * from tbl_Test

where rownum <= ROW_NUM;

END TESTPROC;

-----------------------------------------

Calling the SPROC from EXCEL 2003

-----------------------------------------

Sub ExcelVBA_Sub()

Dim mobjConn As ADODB.Connection

Dim mobjCmd As ADODB.Command

Dim mobjRst As ADODB.Recordset


mobjConn.ConnectionString = "Provider=MSDAORA.1;Password=[your password];User ID=[your UID];Data Source=[Your

Datasource];Persist Security Info=True"

mobjConn.Open




' The command text is your SPROC name with any input parameters following inside brackets (in this case I'm saying I want

5 rows back)

mobjCmd.CommandText = "TESTPROC(5)"

' Open the Recordset


' This is the easiest way to dump the contents of the RS to a sheet that I've found... no messing around with Move .Next

Worksheets(1).Range("A1").CopyFromRecordset mobjRst

mobjRst.Close


End Sub



Sun, 08/29/2010 - 08:00 — Anonymous

Tue, 08/03/2010 - 17:34 — Carolin (not verified)

Thu, 07/15/2010 - 08:38 — Anonymous (not verified)

Tue , 11/17/2009 - 05:34 — Sebastian (not verified)

-----------------

and that's it.... your SPROC data is in excel.

Other info that might help;

You need to make sure you've got the right ADO reference in your VBA project (I had the 2.7 library).

The other thing that took me a little while to work out was that the data source what the name from the TNSnames.ora file

(effectively an alias) rather than server address / db name or any concatenation thereof....

Mine was here: C:\oracle\ora92\network \ADMIN

Though some other references I found on the web had it under program files... anyway. not too hard to find.

Hopefully this will save someone some time!

reply

vb6 adodc connectivity addnew & update

I already connect the Msaccess with VB using adodc .I want to save my record in new field of the database

reply

please help me..........

please help me..........

I already connect the Msaccess with VB using adodc.The records are overwite .I want tso save my record in new field of the

database

reply

list

list list1,"student","studentname",studentno","studentname like '"& text1 .text &"'

reply

Thanks a Ton ....

Hi,r



Fri, 10/30/2009 - 16:51 — bkt (not verified)

Tue , 10/27/2009 - 01:40 — silversky78

Thu, 08/13/2009 - 00:42 — wakhuta

Fri, 08/07/2009 - 10:48 — Dr Gordon Rankine (not verified)

Thanks a ton for the briliant tutorial...as i was googling for this kind of work... and i got what i searched for.

Thanks once again.

Sebastian.

reply

vb

how to use data grite for viwe hole data base on the form

reply

NICE!

A very helpful tutorial especially when you are using ADODB. :)

reply

Awesome

Nice tutorial. Easy and quick to understand.

Gat one problem: am failing to connect to sql server database. My database (mydb.mdf) is in same folder as vb6

application, server name is (Wak-Pc).

may you give me a clear explanation on connecting to sql server with vb6.

Keep it up Mr. VB

reply

Stored procedures for Access/SQL/Oracle

Sirs,

This article is first rate, with clear dialogue, examples, and support projects and corresponding code.

Furthermore, although I can't comment on the Oracle element , I have tested the rest, and it helped me enormously for both

my Access and SQL Server 2005 applications.. This material gave me an understanding on the topic, examples with which

to practice and experiment, and a solid platform for my immediate needs.



Wed , 03/24/2010 - 20:10 — Anonymous (not verified)

Tue, 08/04/2009 - 21:35 — popeto

Tue, 07/28/2009 - 23:05 — vb6lover (not verified)

Thu, 04/29/2010 - 13:15 — Tom R (not verified)

I only wish there were more articles and "How to ..." like this available.

Well done, and many thanks

Dr. Gordon Rankine, Scotland

reply

Great

The sample code for Access and SQL was great. Thanks a lot it was a great help. :)

Regards,

David Reyes III

reply

ado access

it awsome man, cant wait to try it, ty!!!

reply

how to add an if-then-else for opening the database?

i mean,

If mobjConn.Open = False Then

Msgbox("Unable to connect to the database")

Else

Msgbox("Connected!")

End If

doesn't work, is there a way to make it does?

reply

The State property lets you



Mon , 02/22/2010 - 12:34 — mtm (not verified)

Fri, 02/06/2009 - 04:06 — Anonymous (not verified)

Wed , 01/28/2009 - 04:13 — Anonymous (not verified)

The State property lets you know if a object is connected or now. It works with Connection and Recordset objects.

Possibly others as well .

True if connected and False if not connected.

--------------------------------------------------------------

Your code:

If mobjConn.Open = False Then


Else


End If

-------------------------------------------------------------------

Adjusted Code:

If not mobjConn.State Then


Else


End If

reply

data base

no idea....

reply

Thanks!

Thank you for this. Really helpful indeed.

reply

Thanks. I needed to return

Thanks. I needed to return values and cursors from Oracle and your examples are just what I was looking for.



Wed, 12/31/2008 - 04:23 — Mohammed Sayeed (not verified)

Tue , 11/25/2008 - 14:42 — Anonymous (not verified)

Sun, 11/02/2008 - 08:20 — Blacksheep (not verified)

reply

Great piece of work

Great piece of work. I am very thankful as I got what I want. The author has the command to demonstrate complicated

things in a very easy and simple way.

Great

Sayeed

reply

Formatting code in HTML

You should put your formatted VB code in an HTML "code" or "pre" element to maintain the formatting (particularly the

indentation).

reply

sybase and visual basic

Hi there. I am using Adaptive server anywhere 9 (sybase). I have a problem with stored procedure. when i insert data with a

varchar type it will save only the first character of the value.

for example :

visual basic code:

cmdCommand.Parameters.Append cmdCommand.CreateParameter("@tempvar", adVarChar, adParamInput, 50, "test")

cmdCommand.CommandText = "test"

cmdCommand.CommandType = adCmdStoredProc

cmdCommand.ActiveConnection = cn

cmdCommand.Execute

stored procedure:

ALTER PROCEDURE "DBA"."test"(in @tempvar varchar(50))

BEGIN

insert into test (name) values (@tempvar);

END



Thu, 02/18/2010 - 08:03 — Adrian Albu (not verified)

Wed , 10/15/2008 - 08:54 — Timothy C . Alvord (not verified)

Fri, 08/29/2008 - 12:28 — BobF (not verified)

result:

name = "t" instead of name = "test"

why does it only save the first character.

I experienced this problem for varchar type only.

Please help!

reply

answer

what I see is that it may be the stored procedure does not have parameters lenght defined

reply

SQL decimal type

In the SQL Stored Procedure I'm calling, the parameters are defined in SQL as decimal(x,y). From VB6, the data I want to

pass is of type Double. How do I setup the .CreateParameter to work correctly.

I tried dbDecimal, but couldn't get it to work correctly. Can I just create the parameter as dbDouble and have it work

correctly in SQL?

reply

ADO and Acces Stored Procedure

This does not work. Error message says it's invalid in this context. I assume that "SelectCustomer" is an existing Querydef in

the Access MDB.


mobjCmd.CommandText = "SelectCustomer"


I have a need to execute a query in access that already exist (querydef). I would just code the SQL statement but it's about

300 plus character statement which there is a 255 limit.

reply



Fri, 08/29/2008 - 03:55 — Zlatko (not verified)

Tue, 08/26/2008 - 21:37 — Dennis Quek (not verified)

Thu, 07/31/2008 - 07:58 — Ricky_Lomax (not verified)

Thu, 12/27/2007 - 23:12 — Anonymous

Fri, 12/14/2007 - 21:46 — Anonymous

Sat, 11/03/2007 - 08:19 — Anonymous

AMAZED

I Just wanna thank you on your excellent work I'm thrilled with the detail of explanation I found here and the simplicity with

which this article was made. Thank you very MUCH

reply

Tis rocks

Although this is a vb6 old article, but your SQL is still quite relevant in today's programming. Was doing a project on stored

procedure, and I guess all that I need can be found here.

Salutes~

reply

The best and more explicit explanation.

La fuerza esta con tigo .....

reply

Stored Proc in VB

Tramendous....keep it up....(Ajit Singh)

reply

Very good and useful. Keep

Very good and useful. Keep it up man

reply

Absolutely Brilliant



Sun, 04/22/2007 - 16:46 — Anonymous

Tue, 04/10/2007 - 08:30 — Anonymous

Hey mister ...you should be lookin at a career in technical writing...if you aren't one already!!!

Brilliant explanations and good english...always a pleasure to read. Two thumbs up!!!

reply

thums up

hey MR. VB it was as if I am looking at MSDN library , Thumbs up

reply

Very nice

This article was very helpful.

reply

Post new comment

Your name:

Anonymous

E-mail:

The content of this field is kept private and will not be shown publicly.

Homepage:

Subject:

Comment: *



You might also find these useful:

Access Security

Using Jet Data Access Objects

Optimizing Database Applications

Database Design

Using DAO (Data Access Objects) Code

Introduction to SQL (Structured Query Language)

Creating Advanced PDF documents in VB

Naming Database Objects

Access SQL

VB6 With Access

Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>

Lines and paragraphs break automatically .

You may post block code using <blockcode [type="language "]>...</blockcode> tags. You may also post inline code using <code

[type=" language"]>...</code> tags.

More information about formatting options

Preview comment

Using ADO and Stored Procedures _ Visual Basic 6 (VB6)

Documents

Transcript of Using ADO and Stored Procedures _ Visual Basic 6 (VB6)