Strange behaviour of ODBC cursor

When i'm opening an ODBC cursor and querying a value, i often get blank values in columns i know contain data..
I open the cursors as forwardonly/static, and i know that records are returned.
Could this be a memory violation?

Code:

char *RecSet::GetData(short colNum){
	char *retVal = new char[101];
	long lLen(0);
	short sRes(0);

	sRes=SQLGetData(this->m_hStmt, colNum, SQL_C_CHAR, retVal, 100,  &lLen);
	if(sRes != SQL_SUCCESS && sRes != SQL_SUCCESS_WITH_INFO){
		delete [] retVal;
		return(0);
	}
	return(retVal);
}

Still no replies..
Maybe the source will help? I'm not even sure the error is in the recordset class.
Unexplainable things seem to happen when i try to use GetData() with the column name instead of the number..

>>Still no replies..
Maybe you should read this . Your question isn't directly C++, is it?

I realize it should be at the Windows board, I don't know why i originally posted it at the c++ board.
I don't have the rights to delete it, thus it's stuck at c++...

I dont use ODBC (prefer ADO via MFC), but it looks like you are assuming all values are stings........and your not checking to see if there's any more additional info such as if there's a data mismatch

Have a look here. Pay attention about the SQLSTATE part

Also, consider the ADO/MFC approach...the technology is current (not legacy like ODBC API), and the use of the Variant wrapper in MFC make's life so much easier

I thought the SQL_C_CHAR was a kind of a variant...

From MSDN:
07006 Restricted data type attribute violation The data value of a column in the result set cannot be converted to the C data type specified by the argument TargetType.

I'll try to dp a typecheck in the getdata function, and print to a char array instead.
I don't think this explains the strange things happening sometimes when i open a cursor:
-Sometimes the main window moves
-Sometimes i get a memory violation(in ODBC32.dll), that's why i figured it was in the recordset class..

Originally posted by knutso
I thought the SQL_C_CHAR was a kind of a variant...

No...a variant is a special type that basically represents any valid data type.....in C++ its often represented as a union with LONG, SHORT, IDispatch, BSTR, LPVOID etc......they are most common in VB when you program with late binding, or if you use VBScript etc..

There are some APIs to work with them, but they are a pain....and so MFC and ATL have a wrapper that handles them.....for instance with ADO, I can get any value from a recordset as a variant and then convert it to what I need (assuming its convertable)