PRB: Error: "Invalid cursor name" & "No cursor name available" (120511)

    CMyRecordSet set;
    set.m_strFilter = "CustNo = ?";
    set.m_CustNoParam = 1;
    set.Open();
    set.m_CustNoParam = 1;
    set.Requery();
    set.Edit();
    set.m_CustNo = 2;
    set.Update();
				

CAUSE

The MFC database classes do not explicitly set a cursor name with the SQLSetCursorName call. Thus the MFC database classes depend on implicit cursor names given by the ODBC driver by default. The 1.0 ODBC Specification did not specify that an implicit cursor remain with the statement handle until the hstmt was dropped. Hence, the implicit cursor name in the SQL Server driver goes away just before the recordset.Update() call in the above example, resulting in the "No Cursor Name available" message when the MFC Database classes call SQLGetCursorName (Line 2421 in the UpdateInsertDelete method in dbcore.cpp).

You can receive the "Invalid cursor name" message under similar circumstances especially after you have traversed a recordset and before requerying.