| title | SQLGetData and Block Cursors | Microsoft Docs | ||||
|---|---|---|---|---|---|
| ms.custom | |||||
| ms.date | 01/19/2017 | ||||
| ms.prod | sql | ||||
| ms.prod_service | connectivity | ||||
| ms.reviewer | |||||
| ms.technology | connectivity | ||||
| ms.topic | conceptual | ||||
| helpviewer_keywords |
|
||||
| ms.assetid | 12599cdc-7725-4faf-bcae-e163ea0f5851 | ||||
| author | David-Engel | ||||
| ms.author | v-daenge |
SQLGetData operates on a single column of a single row and cannot fetch an array containing data from multiple rows. This is because the primary use of SQLGetData is to fetch long data in parts, and there is little or no reason to do this for more than one row at a time.
To use SQLGetData with a block cursor, an application first calls SQLSetPos to position the cursor on a single row. It then calls SQLGetData for a column in that row. However, this behavior is optional. To determine if a driver supports the use of SQLGetData with block cursors, an application calls SQLGetInfo with the SQL_GETDATA_EXTENSIONS option.