Home   |   Asp.Net 2.0   |   .Net Framework 2.0   |   IIS 6.0   |   Sql Server 2005   |   Visual Basic 2005   |   c# 2005   |   VS 2005   |   Visual Source Safe 2005

MS Dynamics CRM 3.0

SharePoint Portal Server 2003
SharePoint Server 2007
Dynamics NAV
Dynamics CRM
SharePoint Designer 2007
SharePoint Portal Server 2001
Windows SharePoint Services
Windows SharePoint Services 3.0
Project Server 2003
Project Server 2007
Dynamics – Point of Sale
Dynamics AX
Dynamics GP
Dynamics Retail Management System (RMS)
Dynamics SL
SQL Server 2000
Visual Basic .NET 2003
Visual C# .NET 2003
Visual C++ .NET 2003
Visual C++ 2005
Visual SourceSafe 6.0
Windows Server 2003
Windows Server 2003
Outlook 2003
ADO.NET 1.1
ASP.NET 1.0
Visual Studio Team Foundation Server
Visual Studio 2005 Team Edition
Windows Internet Explorer 7
BizTalk Server 2000
BizTalk Server 2002
BizTalk Server 2004
BizTalk Server 2006
Visual Studio 6.0
Access 2000
Access 2002
Access 2003
Access 2007
Access 97
Collaboration Data Objects 2.0
Commerce Server 2002
Content Management Server 2001
Commerce Server 2007
Content Management Server 2002
Data Access Components 2.7
Data Access Components 2.8
DirectX 9.0b
Office Small Business Accounting 2006
Accounting 2007
ActiveSync 4.1
Class Server 2.0
Groove 2007
Windows Vista
Outlook 2007
OneNote 2003
OneNote 2007
Office X for Mac
Zune software
Zune Live
Zoo Tycoon 2
Flight Simulator 2002
Dungeon Siege II

Cervo Technologies
The Right Source to Outsource

Oracle Database FAQS

Sharepoint Portal Server KB

Outlook 2007 Knowledge Base Articles

Data Access Components 2.7 Knowledge Base Articles

When an ActiveX Data Objects (ADO) recordset is marshalled out-of-process while an AddNew method is pending on the recordset, the result is that strings are set to zero length strings and numeric fields are set to zero. This behavior is by design....


When an ActiveX Data Objects (ADO) recordset is marshalled out-of-process while an AddNew method is pending on the recordset, the result is that strings are set to zero length strings and numeric fields are set to zero.

STATUS

This behavior is by design. Therefore, to avoid possible errors within your applications, Microsoft recommends that you either first save the current record or explicitly set all the values as appropriate before the recordset is marshalled.

MORE INFORMATION

When marshalling a recordset across apartment boundaries from one component to another while an AddNew is pending on the recordset, it is strongly suggested that the component explicitly set the column values as expected prior to marshalling the recordset. If a recordset is marshalled during an AddNew without the respective Update operation being invoked, all character fields are set to zero length strings and numeric columns are set to zero. Any component that receives the marshalled recordset must account for this behavior. This behavior is by design when marshalling any object and is not specific to ADO. It is the developer's responsibility to explicitly set column values to an appropriate value or NULL prior to marshalling the recordset.


APPLIES TO
Microsoft Data Access Components 1.5
Microsoft Data Access Components 2.8
Microsoft Data Access Components 2.0
Microsoft Data Access Components 2.1
Microsoft Data Access Components 2.1 Service Pack 2
Microsoft Data Access Components 2.1 Service Pack 1
Microsoft Data Access Components 2.1 Service Pack 2
Microsoft Data Access Components 2.5
Microsoft Data Access Components 2.5 Service Pack 1
Microsoft Data Access Components 2.6
Microsoft Data Access Components 2.7

Keywords: 
kbprb kbfaq KB271553

Copyright © 2004 - 2007 Gridview.org, Inc. All rights reserved. Powered by Smart Web Content Management System