Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Readme_Processing Return Codes and Output Parameters (ODBC)

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.

This sample shows processing a return code and output parameter. This sample is not supported on IA64.

SQL Server samples and sample databases must be downloaded and installed before you can view or work with them. For more information, see Considerations for Installing SQL Server Samples and Sample Databases.

For more information on this sample, see How to: Process Return Codes and Output Parameters (ODBC) in Books Online.

This sample uses Visual C++.

Before running this sample, make sure the following software is installed:

  • SQL Server or SQL Server Express including Database Engine.
    You can download SQL Server Express from the Microsoft Download Center.
  • The AdventureWorks2008R2 database that is available at the Microsoft SQL Server Developer Center.
  • The SQL Server Database Engine samples that are available at the Microsoft SQL Server Developer Center.
  • .NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See Installing the .NET Framework Documentation.
  • You will also need an ODBC data source called AdventureWorks, whose default database is the AdventureWorks sample database. If you will build and run this sample as a 32-bit application on a 64-bit operating system, you must create the ODBC data source with the ODBC Administrator in %windir%\SysWOW64\odbcad32.exe.

  • This sample connects to your computer's default SQL Server instance. To connect to a named instance, change the definition of the ODBC data source to specify the instance using the following format: server\named_instance. By default, SQL Server Express installs to a named instance.
  • The sample requires you to execute the following stored procedure, which you can find in the sample's scripts directory:
    use AdventureWorks
    IF EXISTS (SELECT name FROM sysobjects WHERE name = 'TestParm')
       DROP PROCEDURE TestParm
    GO
    
    CREATE PROCEDURE TestParm 
    @OutParm int OUTPUT 
    AS
    SELECT Name FROM Purchasing.Vendor
    SELECT @OutParm = 88
    RETURN 99
    go
    
    In SQL Server Management Studio, load and execute the Scripts\setup.sql script or execute the following command in a Command Prompt window:
    sqlcmd -E -I -i Scripts\setup.sql
    
  • If you are using Visual Studio, load the ProcessReturnCodes.sln file and build it.
  • If you are using MSBuild.exe, invoke MSBuild.exe in a Command Prompt, passing it the ProcessReturnCodes.sln file:
    MSBuild ProcessReturnCodes.sln
    

  • From Visual Studio, invoke Start Without Debugging (CTRL+F5).
  • If you built with MSBuild.exe, invoke ProcessReturnCodes.exe.

Community Additions

Show:
© 2015 Microsoft