Operation Manual

The Command dialog box appears.

3. Enter a name for the command, select a connection to the database containing the stored procedure, and then select Stored

Procedure from the Type pop-up menu.

4. Select your stored procedure by expanding the Stored Procedures branch in the Database Items box, selecting the stored

procedure from the list, and clicking the Procedure button.

5. Enter any required parameters in the Variables table.

You don’t need to enter any parameters for any RETURN_VALUE variable.

6. Click OK.

After you close the dialog box, ASP code is inserted in your page. When the code runs on the server, the code creates a

command object that runs a stored procedure in the database. The stored procedure in turn performs a database operation,

such as inserting a record.

By default, the code sets the Prepared property of the Command object to true, which makes the application server reuse a

single compiled version of the object every time the stored procedure is run. If you know the command will be executed more

than a few times, having a single compiled version of the object can improve the efficiency of database operations. However,

if the command will only be executed one or two times, using one might actually slow down your web application because the

system has to pause to compile the command. To change the setting, switch to Code view and change the Prepared property

to false.

Note: Not all database providers support prepared commands. If your database does not support it, you might get an error

message when you run the page. Switch to Code view and change the Prepared property to false.

If the stored procedure takes parameters, you might create a page that gathers the parameter values and submits them to the

page with the stored procedure. For example, you may create a page that uses URL parameters or an HTML form to gather

parameter values from users.