AnsweredAssumed Answered

ODBC - Connecting data source causes error: "No cursor open for statement"

Question asked by SamStokell on Sep 11, 2014
Latest reply on May 12, 2015 by TSGal

Summary

ODBC - Connecting data source causes error: "No cursor open for statement"

Product

FileMaker Pro

Version

13

Operating system version

Windows Server 2008

Description of the issue

I am trying to connect my Jade (Object Oriented Programming Language) to FileMaker via ODBC.

For unknown reasons FileMaker is returning that the cursor is not open from the Fetch call.

The call order as shown below taken from the SQL log file is GetTypeInfo, Fetch and then a Close Cursor call (presumably so that the allocated handle can be reused).

Steps to reproduce the problem

jadegt          1850-92c     ENTER SQLGetTypeInfo
          HSTMT               0x02877F58
          SWORD                       -1

jadegt          1850-92c     EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
          HSTMT               0x02877F58
          SWORD                       -1

jadegt          1850-92c     ENTER SQLFetch
          HSTMT               0x02877F58

jadegt          1850-92c     EXIT  SQLFetch  with return code 100 (SQL_NO_DATA_FOUND)
          HSTMT               0x02877F58

jadegt          1850-92c     ENTER SQLCloseCursor
          SQLHSTMT            0x02877F58

jadegt          1850-92c     EXIT  SQLCloseCursor  with return code -1 (SQL_ERROR)
          SQLHSTMT            0x02877F58

          DIAG [HY000] [FileMaker][FileMaker] No cursor open for statement (3066)

Expected result

I am expecting to use FileMaker as a datasource using ODBC

Actual result

We are getting an error that is preventing the setup

Exact text of any error message(s) that appear

No cursor open for statement

Configuration information

I am not using FileMaker server to make the connection between the 2 systems. I am just using FileMaker pro then running the listener manually.

Outcomes