Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2003
    Posts
    3

    Unanswered: Error (1552) ODBC, Insert Execute Error

    Hi, I have a program called dbms/copy that I use to conver clarion database tables. The program first creates the table, if already exists I delete and recreate. This part works fine. When it tries to insert the records I get the following error message:

    Error (1552)

    ODBC, Insert Execute Error -> Buffer Contained 100 Records but only 0 Records were written

    I created a System DSN ODBC link to the SQL Server. I tried using the "sa" user, as well as creating a user and checking off all available permissions. It seems to be a permissions problem to me, although it appears I have permission to do everything. It is definately able to connect since it has no problem creating/deleting/recreating the table in the SQL Server database.

    I tried doing the same import with an ODBC connection to a Microsoft Access database and it works without any problems.

    Any idea what's giving me this error?
    Last edited by UltraSmooth; 09-10-03 at 10:20.

  2. #2
    Join Date
    Sep 2003
    Posts
    3

    Re: Error (1552) ODBC, Insert Execute Error

    I turned on ODBC tracing and the following errors showed up in the SQL.log file:

    dbmswin7 f58-b90 ENTER SQLSetStmtAttr
    SQLHSTMT 00E51F98
    SQLINTEGER 6 <SQL_ATTR_CURSOR_TYPE>
    SQLPOINTER 0x00000001
    SQLINTEGER 0

    dbmswin7 f58-b90 EXIT SQLSetStmtAttr with return code -1 (SQL_ERROR)
    SQLHSTMT 00E51F98
    SQLINTEGER 6 <SQL_ATTR_CURSOR_TYPE>
    SQLPOINTER 0x00000001
    SQLINTEGER 0

    DIAG [24000] [Microsoft][ODBC Driver Manager] Invalid cursor state (0)

    dbmswin7 f58-b90 ENTER SQLSetStmtAttr
    SQLHSTMT 00E51F98
    SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
    SQLPOINTER 0x00000003
    SQLINTEGER 0

    dbmswin7 f58-b90 EXIT SQLSetStmtAttr with return code -1 (SQL_ERROR)
    SQLHSTMT 00E51F98
    SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
    SQLPOINTER 0x00000003
    SQLINTEGER 0

    DIAG [24000] [Microsoft][ODBC Driver Manager] Invalid cursor state (0)

    dbmswin7 f58-b90 ENTER SQLSetStmtAttr
    SQLHSTMT 00E51F98
    SQLINTEGER 5 <SQL_ATTR_ROW_BIND_TYPE>
    SQLPOINTER 0x00000000
    SQLINTEGER 0

    dbmswin7 f58-b90 EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
    SQLHSTMT 00E51F98
    SQLINTEGER 5 <SQL_ATTR_ROW_BIND_TYPE>
    SQLPOINTER 0x00000000
    SQLINTEGER 0

    dbmswin7 f58-b90 ENTER SQLSetStmtAttr
    SQLHSTMT 00E51F98
    SQLINTEGER 27 <SQL_ATTR_ROW_ARRAY_SIZE>
    SQLPOINTER 0x00000064
    SQLINTEGER 0

    dbmswin7 f58-b90 EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
    SQLHSTMT 00E51F98
    SQLINTEGER 27 <SQL_ATTR_ROW_ARRAY_SIZE>
    SQLPOINTER 0x00000064 (BADMEM)
    SQLINTEGER 0

    dbmswin7 f58-b90 ENTER SQLBulkOperations
    SQLHSTMT 00E51F98
    SQLSMALLINT 4

    dbmswin7 f58-b90 EXIT SQLBulkOperations with return code -1 (SQL_ERROR)
    SQLHSTMT 00E51F98
    SQLSMALLINT 4

    DIAG [S1092] [Microsoft][ODBC SQL Server Driver]Invalid attribute/option identifier (0)

    dbmswin7 f58-b90 ENTER SQLRowCount
    HSTMT 00E51F98
    SQLLEN * 0x0012F7F4

    dbmswin7 f58-b90 EXIT SQLRowCount with return code 0 (SQL_SUCCESS)
    HSTMT 00E51F98
    SQLLEN * 0x0012F7F4 (0)

    dbmswin7 f58-b90 ENTER SQLDisconnect
    HDBC 00E515E8

    dbmswin7 f58-b90 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
    HDBC 00E515E8



    Originally posted by UltraSmooth
    Hi, I have a program called dbms/copy that I use to conver clarion database tables. The program first creates the table, if already exists I delete and recreate. This part works fine. When it tries to insert the records I get the following error message:

    Error (1552)

    ODBC, Insert Execute Error -> Buffer Contained 100 Records but only 0 Records were written

    I created a System DSN ODBC link to the SQL Server. I tried using the "sa" user, as well as creating a user and checking off all available permissions. It seems to be a permissions problem to me, although it appears I have permission to do everything. It is definately able to connect since it has no problem creating/deleting/recreating the table in the SQL Server database.

    I tried doing the same import with an ODBC connection to a Microsoft Access database and it works without any problems.

    Any idea what's giving me this error?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •