Re: QZDASOINIT SQL attributes?

Glad it's working - I just wish IBM developers had handled this better.

Vern

At 03:22 PM 12/20/2005, you wrote:

Vernon, a small update on this problem.

As mentioned, patching the data made the trick, tough this wasn't very elegant... So, I had an idea: what about Start/Configuration/ControlPanel/RegionalConfiguration in Windows? (sorry if these names don't match the english ones... I'm just guessing what they might look like in english...) I started from scratch, with the original VB program and data..., changed my RegionalConfig to using '.' for decimal point (and, obviously ',' for thousands separator...) and, voila, it also worked! So, when QZDASOINIT was complaining about SQL token '.' invalid (both with AS/400 QDECFMT system value set to either 1=' ', or 2='J' , in any case...) was NOT a problem from the AS/400 stand point, but rather Windows? This, to me, seems a little crazy, but anyway, it now seems a bit more clear ... Whenever I have again this kind of problem, changing Windows environment might do the trick... Isn't this funny?

Vernon Hamberg escribió:

Antonio, did you look in the index tab for drivers? Was "Client Access" or "iSeries Access" listed? If so, then the VB program can use ODBC without using a DSN. That is what I think is happening here, and there is no way I know of to change the decimal point in that case - the developer should have retrieved that from the Windows environment. But these are somewhat quickly put together, I think. Perhaps there is a link on the download page where you can respond. Tell IBM about this problem, they might fix it.

Glad you got it fixed!

Vern

At 04:14 PM 12/19/2005, you wrote:

Chris, thanks for the suggestion.

Coudn't try it until today, but... when I read your answer, I kind of questioned it, but wasn't sure.

Correct me if I'm worng:

The PC I run the PC program from has, obviuosly, Client Access installed, but it's a PC I'd never used before with neither ODBC, nor with ADO/OLE/DB. What I mean is, when I went to see ODBC sources as you mentioned, there were no Data Sources of any kind (neither User, nor System, nor File type, just in case, for Vernon Hamberg thoughts) defined to the AS/400. So, I guess the VB program is NOT using ODBC at all to AS/400. Rather, if it is going to set up an environment for ADO/OLE/DB it rather might be using OLE/DB itself, shouldn't it? In any case, to check your suggestion, I created a System DSN to AS/400. Decimal period was set to '.' first, then to ',' a second time.Re-tried the VB program, with same erros as before. I must say, indeed, I did not have any chance to tell the program to use the DSN

I had just created!

I ended up doing things as should never be done: patched the (VB .exe) object program with UEdit32, changing the decimal point (data) to decimal comma in all data being inserted to PARTS file, and it worked! I only miss I'll never end up knowing why it failed...

Any suggestions?

------------------------------------------------------------------------------------------------

Chris Bipes escribió:

On you PC you are running the program from, check the OBDC, ADO OLE/DB
connection properties.  That is where you specify your decimal point for
the connection.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

707.586.0551, ext. 1102
707.585.5700 FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.


-----Original Message-----

Folks, I have a problem:

Trying to set up a sample of ADO OLE/DB environment for VB/Delphi to iSeries. Downloaded the ADO OLE/DB samples from http://www-03.ibm.com/servers/eserver/iseries/access/toolkit/adooledb.ht

m

Once installed, you need to "set up the environment for the server" (i.e. the AS/400), which means creating a Library, ACTIVEXSDK, and some files Customers, Parts, etc) plus some other objects (DTAQ's, etc). A program, "vbass1oledb.exe" will do all that for you. So far so good, but... Problem?

Program "vbass1oledb.exe" starts, from the PC side, creating the library

in the AS/400, and some files, etc and then will populate those files with some sample data, with SQL sentences like:

Insert into Activexsdk.Parts VALUES(12301, 'Quad ...', 44, 120.00, '1996-01-12'

Well, here QZDASOINIT fails with SQL0104 : Token "." not valid ...

The reason is the "decimal point" in the fourth value above (item price)

of 120.00

Obviously, it was meant for the US market, with "decimal point" instead of "decimal comma" which is our standard...

Shouldn't QDECFMT be good enough for that purpose? Any ideas?

--
Antonio Fernandez-Vicenti
afvaiv@xxxxxxxxxxxxxx



--
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.

--
Antonio Fernandez-Vicenti
afvaiv@xxxxxxxxxxxxxx



--
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.