× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Patrick,
if I understand you correctly, when you use German version of BPCS, everything
works fine, while if you try to access BPCS files on your server directly
through ODBC, you don't get proper data because you are not using proper NLV
conversion table for ODBC access. If this is the case, I believe that BPCS
client does NLV translation between English and German by using the conversion
table called NLSE273.TBL, which resides in one of BPCS folders on your PC. I
don't know if you would be able to use this table directly for ODBC (I would
guess not), but you could use it to get the idea if you are able to build
similar conversion table for ODBC.
Hope this helps,
Goran


>Sorry if this is not mutch related with BPCS but I think I have a chance of
>finding an answer here.

>I want to read data from the BPCS tables via ODBC (microsoft access). >But
>the tables have CCSID 37 and its on a german OS/400 with CCSID 273. The >BPCS
>client makes use of the convertor table
>and puts CCSID 237 characters in the 37 tables. When I read these via
>ODBC/access I get all the correct A-Z and 1-9 characters but not the >other
>character( 

Ü --> !). Is there a solution for this problem?
>I have tried with the characters conversion overrides options in the >client
>access properties. I also know that you can use a translation dll in >the
>odbc system dsn. But where can I find one? OR how can I write one?

>If someone knows this please let me know.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.