manager: "sonalm"

[Attributes Property Example (VB)](../../../ado/reference/adox-api/attributes-property-example-vb.md)

The [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] uses the JDBC basic data types to convert the [!INCLUDE[ssNoVersion](../../includes/ssnoversion_md.md)] data types to a format that can be understood by the Java programming language, and vice versa. The JDBC driver provides support for the JDBC 4.0 API, which includes the **SQLXML** data type, and National (Unicode) data types, such as **NCHAR**, **NVARCHAR**, **LONGNVARCHAR**, and **NCLOB**.

|uniqueidentifier|CHAR|String|

|varbinary|VARBINARY|byte[]|

|varbinary(max)|VARBINARY|byte[]|

|varchar|VARCHAR|String|

|varchar(max)|VARCHAR|String|

|xml|LONGVARCHAR<br /><br /> LONGNVARCHAR (Java SE 6.0)|String<br /><br /> SQLXML|

ODBC C data types indicate the data type of C buffers used to store data in the application.

All drivers must support all C data types. This is required because all drivers must support all C types to which SQL types that they support can be converted, and all drivers support at least one character SQL type. Because the character SQL type can be converted to and from all C types, all drivers must support all C types.

[e] A number is stored in the *val* field of the SQL_NUMERIC_STRUCT structure as a scaled integer, in little endian mode (the leftmost byte being the least-significant byte). For example, the number 10.001 base 10, with a scale of 4, is scaled to an integer of 100010. Because this is 186AA in hexadecimal format, the value in SQL_NUMERIC_STRUCT would be "AA 86 01 00 00 ... 00", with the number of bytes defined by the SQL_MAX_NUMERIC_LEN **#define**.

[f] The precision and scale fields of the SQL_C_NUMERIC data type areused for input from an application and for output from the driver to the application. When the driver writes a numeric value into the SQL_NUMERIC_STRUCT, it will use its own driver-specific default as the value for the *precision* field, and it will use the value in the SQL_DESC_SCALE field of the application descriptor (which defaults to 0) for the *scale* field. An application can provide its own values for precision and scale by setting the SQL_DESC_PRECISION and SQL_DESC_SCALE fields of the application descriptor.

**Conformance**

Version Introduced: ODBC 1.0 Standards Compliance: ISO 92

When **SQLGetFunctions** returns SQL_ERROR or SQL_SUCCESS_WITH_INFO, an associated SQLSTATE value can be obtained by calling **SQLGetDiagRec** with a *HandleType* of SQL_HANDLE_DBC and a *Handle* of *ConnectionHandle*. The following table lists the SQLSTATE values commonly returned by **SQLGetFunctions** and explains each one in the context of this function; the notation "(DM)" precedes the descriptions of SQLSTATEs returned by the Driver Manager. The return code associated with each SQLSTATE value is SQL_ERROR, unless noted otherwise.

|SQLSTATE|Error|Description|

|01000|General warning|Driver-specific informational message. (Function returns SQL_SUCCESS_WITH_INFO.)|

|08S01|Communication link failure|The communication link between the driver and the data source to which the driver was connected failed before the function completed processing.|

|HY000|General error|An error occurred for which there was no specific SQLSTATE and for which no implementation-specific SQLSTATE was defined. The error message returned by **SQLGetDiagRec** in the *\*MessageText* buffer describes the error and its cause.|

The following is a list of valid values for *FunctionId* for functions introduced in ODBC 3.8 or later:

[2] **SQLCancelHandle** will be returned as supported only if the driver supports both **SQLCancel** and **SQLCancelHandle**. If **SQLCancel** is supported but **SQLCancelHandle** is not, the application can still call **SQLCancelHandle** on a statement handle, because it will be mapped to **SQLCancel**.

This section is about securing database passwords and the procedure to import or export them across servers:

1. Securing Password

The server definition ids and its corresponding encrypted passwords are stored in a file on the local machine

|-|

|**Example 1:**<br /><br />*Specify password*<br /><br />`C:\SSMA\SSMAforAccessConsole.EXE –securepassword –add all –s “ D:\Program Files\Microsoft SQL Server Migration Assistant for Access\Sample Console Scripts\AssessmentReportGenerationSample.xml” –v “D:\Program Files\Microsoft SQL Server Migration Assistant for Access\Sample Console Scripts\ VariableValueFileSample.xml”`<br /><br />`Enter password for server_id ‘XXX_1’: xxxxxxx`<br /><br />`Re-enter password for server_id ‘XXX_1’: xxxxxxx`|

|**Example 2:**<br /><br />`C:\SSMA\SSMAforAccessConsole.EXE –securepassword –add “source_1,target_1” –c “D:\Program Files\Microsoft SQL Server Migration Assistant for Access\Sample Console Scripts\ServersConnectionFileSample.xml” – v “D:\Program Files\Microsoft SQL Server Migration Assistant for Access\Sample Console Scripts\ VariableValueFileSample.xml” -o`<br /><br />`Enter password for server_id ‘source_1’: xxxxxxx`<br /><br />`Re-enter password for server_id ‘source_1’: xxxxxxx`<br /><br />`Enter password for server_id ‘target_1’: xxxxxxx`<br /><br />`Re-enter password for server_id ‘target _1’: xxxxxxx`|

Execute the `SSMAforAccessConsole.exe` with the`–securepassword` and `–remove` switch at command line passing the server ids, to remove the encrypted passwords from the protected storage file present on the local machine.

|`C:\SSMA\SSMAforAccessConsole.EXE –securepassword –remove all`C:\SSMA\SSMAforAccessConsole.EXE –securepassword –remove “source_1,target_1”|

- **Listing Server Ids whose passwords are encrypted**

Execute the SSMAforAccessConsole.exe with the `–securepassword` and `–list` switch at command line to list all the server ids whose passwords have been encrypted.

|`C:\SSMA\SSMAforAccessConsole.EXE –securepassword –list`|

> [!NOTE]

The SSMA Console application allows you to export encrypted database passwords present in a file on the local machine to a secured file and vice-versa. It helps in making the encrypted passwords machine independent. Export functionality reads the server id and password from the local protected storage and saves the information in an encrypted file. The user is prompted to enter the password for the secured file. Make sure the password entered is 8 character length or more. This secured file is portable across different machines. Import functionality reads the server id and password information from the secured file. The user is prompted to enter the password for the secured file and appends the information to the local protected storage.

[Executing the SSMA Console (Access)](http://msdn.microsoft.com/en-us/aa1bf665-8dc0-4259-b36f-46ae67197a43)