BUG: ESQL: SQLD Is Set Incorrectly with Some Prepared Queries

• Microsoft Embedded SQL version 4.21 for COBOL

SYMPTOMS

The PREPARE statement may incorrectly set SQLD to zero if the prepared statement is a SELECT query with ORDER BY, or UNIONed with another SELECT query.

In the case of ORDER BY, the problem will occur if the ORDER BY is on a column that does not have any clustered indexes. For example:

   select * from authors order by au_lname

   select * from authors order by au_id

In case of UNION, any two SELECT statements that are UNIONed together will have SQLD set incorrectly.

This SQLD is supposed to be set to the number of columns the prepared SELECT query returns, and to zero if the prepared query does not return any results.

CAUSE

SQL Server Embedded SQL for COBOL incorrectly set the SQLD value if the prepared statement contains ORDER BY on a column without a clustered index, or if UNION is used in the query.

STATUS

Microsoft has confirmed this to be a problem in Embedded SQL version 4.21 for COBOL. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.