Difference between revisions of "Error Messages/43122"

Revision as of 21:07, 29 February 2016

Example error message

HY010: [Microsoft][ODBC Driver Manager] Function sequence error.

Causes

Empty SQL

This error is encountered when the SQL parameter to DbQuery is empty text, "".

Microsoft description

Microsoft's documentation has this (cryptic) explanation of the HY010 error:

(DM) An asynchronously executing function was called for a StatementHandle associated with the ConnectionHandle and was still executing when SQLDisconnect was called.

(DM) An asynchronously executing function (not this one) was called for the ConnectionHandle and was still executing when this function was called.

(DM) SQLExecute, SQLExecDirect, SQLBulkOperations, or SQLSetPos was called for a StatementHandle associated with the ConnectionHandle and returned SQL_NEED_DATA. This function was called before data was sent for all data-at-execution parameters or columns.

@@ Line 1: / Line 1: @@
-= Example Error Message =
+[[Category: Error messages]]
-:HY010:[Microsoft][ODBC Driver Manager] Function sequence error.
+== Example error message ==
+:<code>''HY010: [Microsoft][ODBC Driver Manager] Function sequence error.''</code>
-= Causes =
+== Causes ==
+=== Empty SQL ===
-== Empty SQL ==
+This error is encountered when the SQL parameter to [[DbQuery]] is empty text, <code>""</code>.
-I encountered this error when the SQL parameter to [[DbQuery]] was empty text, <code>""</code>.
+=== Microsoft description ===
-== Microsoft description ==
+Microsoft's documentation has this (cryptic) explanation of the <code>HY010</code> error:
-Microsoft's documentation has this (cryptic) explanation of HY010:
+:''(DM) An asynchronously executing function was called for a StatementHandle associated with the ConnectionHandle and was still executing when SQLDisconnect was called.''
+:''(DM) An asynchronously executing function (not this one) was called for the ConnectionHandle and was still executing when this function was called.''
+:''(DM) SQLExecute, SQLExecDirect, SQLBulkOperations, or SQLSetPos was called for a StatementHandle associated with the ConnectionHandle and returned SQL_NEED_DATA. This function was called before data was sent for all data-at-execution parameters or columns.''
-:(DM) An asynchronously executing function was called for a StatementHandle associated with the ConnectionHandle and was still executing when SQLDisconnect was called.
+==See Also==
-:(DM) An asynchronously executing function (not this one) was called for the ConnectionHandle and was still executing when this function was called.
+* [[DbQuery]]
-:(DM) SQLExecute, SQLExecDirect, SQLBulkOperations, or SQLSetPos was called for a StatementHandle associated with the ConnectionHandle and returned SQL_NEED_DATA. This function was called before data was sent for all data-at-execution parameters or columns.
+* [[DbQuery/Step-by-Step querying Microsoft Access]]
+* [[Querying Access database from Analytica 64]]