What product and version number are you using?

How are you linking the program, shared, dynamic, static?

So you are stating that the program works OK, connects to the database, runs SQL statements, etc for an hour and then gets this error?

That doesn't make sense as _SQLODBC is an entry point into the OpenESQL run-time system which should already be loaded at that point in time.

Does this problem occur everytime you run the application after about an hour?

Does it occur at any particular location within the program?

You might consider tunring on the ODBC tracing using one of the following directives:

ODBCTRACE=ALWAYS

TRACELEVEL=4

Thanks.

Thanks...

I'm running the ODBC trace to find the statement that causes the error ,

- i have attached mfsupportinfo.log

- the program is linked shared and this problem occur everytime I run app

- I will also trace with ODBCTRACE= ALWAYS and TRACELEVEL=4

Hi,

I have solved the error by installing the latest version of the ODBC driver for MSSQL.

However, after making the ODBC trace I found many lines with message "badmem" like this:

ODBCRUN.EXE LB B4C-c78 EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
SQLHSTMT 016E7A50
SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
SQLPOINTER 0x00000001 (badmem)
SQLINTEGER -5

While the ESQL TRACE is not come to end due to lack of disk space, the log written had exceeded 5 Gb, after 7 hours ...

Again, thanks for your time

greetings...

this error has come back on another installation...