RE: ODBC SQLINTEGER & (BADMEM) - Why?
- From: v-sguo@xxxxxxxxxxxxxxxxxxxx (Sophie Guo [MSFT])
- Date: Thu, 27 Oct 2005 09:32:24 GMT
Hello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Prev by Date: RE: ODBC Error with Sybase from Win2K Server (but works from WinXP!)
- Next by Date: 3197 record deleted error
- Previous by thread: Re: relinking tables using MS Access
- Next by thread: 3197 record deleted error
- Index(es):
Loading