Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 191453 - Last Review: October 6, 2004 - Revision: 4.1
BUG: Conversion from OS/390 PACKED to DECIMAL and NUMERIC fails
This article was previously published under Q191453
An attempt to display an IBM OS/390 packed decimal record field as
converted to the DECIMAL or NUMERIC automation type results in errors. The
first manifestation, generally, is that there is no data to display, for
example, in a Visual Basic text box.
Packed decimal fields can be converted to a string (DBTYPE_STR, CHAR)
successfully.
Microsoft has confirmed this to be a problem in the OLE DB Provider for
AS/400 and VSAM component of Microsoft SNA Server version 4.0 SP1.
An attempt to convert an IBM OS/390 packed decimal record field to either
the NUMERIC (DBTYPE_NUMERIC) or DECIMAL (DBTYPE_DECIMAL) automation types
results in the following error manifestations. They are seen when running a
Visual Basic consumer in debug mode.
- A watch is added for the ADO recordset, and the value of the numeric
field is set to "Errors occurred".
- When an immediate statement to view the numeric field s executed, for
example, "? RS.Fields(10).Value<enter>," the following message box
appears:
Title Bar: Microsoft Visual Basic
Description: HRESULT 80040e21 (-2147217887)
Errors occurred.
- An attempt to display this field/column in a text box yields either
blanks or nothing.
- Issuing an ADO GetRows results in an error being returned from OLE DB
Provider with the same HRESULT, -2147217887 (0x80040e21) and the
description "Automation error."
APPLIES TO
- Microsoft OLE DB Provider for AS/400 and VSAM 1.0, when used with:
- Microsoft SNA Server 4.0 Service Pack 1
| kbbug kbpending kbsnaonly KB191453 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate