Re: OLEDB error with SQL 2005
- From: "Radzi" <imradzi@xxxxxxxxx>
- Date: 11 Jul 2006 19:04:32 -0700
Hi,
It's hard to show my code becuase I've created classes that handles all
the OLEDB setting and calls... I believe perhaps some of the parameter
were not correctly set; but was OK in the SQL 2000...
I will try flatten the code in near future.
Thanks.
Erland Sommarskog wrote:
Radzi (imradzi@xxxxxxxxx) writes:
It still didn't work. Same problem with SQLNCLI or with SQLOLEDB. Still
could not find why this is happening. My workaround for the time being
is to pass all string as empty string instead of setting status flag to
DBSTATUS_ISNULL, and modify my stored-procedure to check if the string
is empty to set the variable to null.
Again, without seeing your code, it's difficult to assist.
All I can say is that I have been able to pass NULL values successfully
to SQL 2005, both with SQL Native Client and SQLOLEDB.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Re: OLEDB error with SQL 2005
- From: Radzi
- Re: OLEDB error with SQL 2005
- From: Erland Sommarskog
- Re: OLEDB error with SQL 2005
- Prev by Date: Re: OLEDB connection string for .MDF (?)
- Next by Date: Re: Data concept
- Previous by thread: Re: OLEDB error with SQL 2005
- Next by thread: Re: DB_E_ERRORSOCCURRED during IRowsetChange::Execute()
- Index(es):
Relevant Pages
|
|
