Article ID: 171910 - Last Review: February 12, 2007 - Revision: 3.1 BUG: If RPC Is Used, SQL Server ODBC Driver Converts in PlaceThis article was previously published under Q171910
BUG #: 17119 (SQL 6.5)
SYMPTOMS
In a self-written ODBC program that executes a prepared statement at a SQL
Server (set up with an OEM code page, such as code page 437 or 850) the
data in the buffer passed in the rgbValue parameter of SQLBindParameter is
converted from ANSI to OEM after issuing the SQLExecute. This can be
observed when using extended characters in the character buffer.
In Microsoft Access, when you retrieve records in an attached ODBC table, each field in a record contains the "#Deleted" error message. This happens if the attached SQL Server table contains extended characters in the primary key of that record. This problem occurs if all of the following conditions are true:
CAUSE
The ODBC SQL Server driver invokes the stored procedure upon SQLExecute by
remote procedure call (RPC). In this scenario, a passed parameter is
converted in place. Because Microsoft Access reuses these parameters to
match the returned data to the values of the primary key, it shows
"#Deleted" in the affected records.
WORKAROUND
To work around this problem, do one of the following, as appropriate for
your application:
STATUS
Microsoft has confirmed this to be a problem in the products listed at the
beginning of this article. We are researching this problem and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
MORE INFORMATION
This problem also occurs if you use the MS Code page Translator instead of
the "Convert OEM to ANSI characters" check box.
APPLIES TO
| Article Translations
|

Back to the top
