Re: VB & ADO don't seem to handle numeric fields

Oops!
Peter, you probably caught my mistake right away, but just in case you
haven't, the line that you need to type in the debugger window should
actually be:
?AS400rs.Fields(n)
Sorry,
John Taylor
Canada
----- Original Message -----
From: "John Taylor" <john.taylor@telusplanet.net>
To: <MIDRANGE-L@midrange.com>
Sent: Monday, November 27, 2000 07:10
Subject: RE: VB & ADO don't seem to handle numeric fields
> Hi Peter,
>
>
> The error message that you're getting typically occurs when the field name
> that you've specified doesn't exist in the recordset. I had a problem a
> couple of months ago with the SQL host server not passing back a field
name
> to the ADO driver. I opened an APAR and the problem was resolved via PTF.
I
> don't have the number handy since I'm at home right now.
>
> You can do a simple test to determine if this is your problem.
>
> Place a breakpoint on the RateAmt line, and set a Watch on AS400rs. Run
the
> program, then expand AS400rs until you find the "RTAMT" field. Make a note
> of the data type & ordinal field position. (Of course, if you can't find
the
> "RTAMT" field, then you've found the problem.)
>
> Using the debugger window, try the following code:
>
> ?RateAmt = AS400rs.Fields(n)
>
> where "n" is the ordinal position.
>
> If you can access the data via ordinal position, then double check your
> spelling. Let us know what you find.
>
>
> Regards,
>
> John Taylor
> Canda
>
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].