Very Computer

by **Philip F. Che** » Fri, 23 Apr 1999 04:00:00

Hi,

I have a fairly simple routine which retrieves a single field. But this
routine will fail after being called exactly 160 times !!!

char* getLastName(char* pId)
{

char* pRetVal = new char(51);
char Statement[255];
sprintf(Statement, "SELECT last_name FROM namemaster WHERE id='%'",
pId);

SQLINTEGER fieldLenOrInd = SQL_NTS;
SQLBindCol(m_hStmt, 1, SQL_C_CHAR, pRetVal, 51, &fieldLenOrInd);

SQLRETURN retcode = SQLExecDirect(m_hStmt, (unsigned char*)&Statement,
SQL_NTS);

retcode = SQLFetch(m_hStmt);

SQLCloseCursor(m_hStmt);

return pRetVal;

Quote:}

For simplicity I removed all error handling, etc. It took me two days to
figure out why. But I haven't got any clue.

Please help if you know anything about it. I am using SQL Server 7.0 and
ODBC 3.510.3513.

Thanks a bounch!

Philip

by **huge** » Sat, 24 Apr 1999 04:00:00

if it fails after 160 times, I would probably look at the data in that
particular field of that particular record.
How does it differ from the previous 159 fields/times it was called?
Have you tried a different source to test against?
How many records are in your set?
Special characters like apostrophes or double quotes or others?

>Hi,

>I have a fairly simple routine which retrieves a single field. But this
>routine will fail after being called exactly 160 times !!!

>char* getLastName(char* pId)
>{

> char* pRetVal = new char(51);
> char Statement[255];
> sprintf(Statement, "SELECT last_name FROM namemaster WHERE id='%'",
>pId);

> SQLINTEGER fieldLenOrInd = SQL_NTS;
> SQLBindCol(m_hStmt, 1, SQL_C_CHAR, pRetVal, 51, &fieldLenOrInd);

> SQLRETURN retcode = SQLExecDirect(m_hStmt, (unsigned char*)&Statement,
>SQL_NTS);

> retcode = SQLFetch(m_hStmt);

> SQLCloseCursor(m_hStmt);

> return pRetVal;
>}

>For simplicity I removed all error handling, etc. It took me two days to
>figure out why. But I haven't got any clue.

>Please help if you know anything about it. I am using SQL Server 7.0 and
>ODBC 3.510.3513.

>Thanks a bounch!

>Philip

Very Computer

weird odbc error

weird odbc error

weird odbc error