|
Yeah, I just discovered that. So now the situation is this: For Operations Navigator, if I go to JDBC setup and check translation, it returns the proper data. If I use the ODBC driver and tell it to translate, it works. But if I use the OLE DB provider, it still doesn't work (no where I know of to implicitly tell it to translate). ----- Original Message ----- From: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, September 30, 2003 9:54 AM Subject: RE: OLE DB returning junk > Sounds like all your files are CCSID 65535, which indicates binary data and > is not translated unless you've checked the "Convert CCSID 65535" property > in your data source. > > Eric DeLong > Sally Beauty Company > MIS-Project Manager (BSG) > 940-898-7863 or ext. 1863 > > > > -----Original Message----- > From: Adam Lang [mailto:aalang@xxxxxxxxxxxxxxxxxxxx] > Sent: Tuesday, September 30, 2003 8:38 AM > To: Midrange Systems Technical Discussion > Subject: Re: OLE DB returning junk > > > I ran the same query in the Run SQL Scripts in Operations NAvigator and it > returned the non translated data as well. > > The as/400 is running 4.4 and i am using CAE 5.1. > > ----- Original Message ----- > From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx> > To: <midrange-l@xxxxxxxxxxxx> > Sent: Monday, September 29, 2003 4:29 PM > Subject: OLE DB returning junk > > > > I am doing a query on the AS/400 from Visual Basic OLE DB and some of the > > fields are returning question marks. Is there a way to set a CCSID value > or > > something via OLE DB? Any other ideas what it could be? When I pull down > > the data via the Excel Add-in and set the CCSID property it comes back ok, > > but if I don't, the fields that I get back in VB with problems also show > up > > in Excel with problems. > > > > Adam Lang > > Systems Engineer > > Rutgers Casualty Insurance Company > > http://www.rutgersinsurance.com > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.