Language specific characters with JDBC

Does anybody know how to insert language specific characters to Oracle tables using JDBC and without the overhead of unicode conversion back and forth?
At the moment, all we can do is to convert those characters to unicode when inserting, and perform a reverse conversion when getting back from a resultset. This is cumbersome in large text data.
Is there a way to configure the RDBMS and/or the operating system for this purpose? We are using Oracle 7.3.4 on Windows NT 4.0 SP5, Oracle JDBC Driver 8.1.6, and Java Web Server 2.0 (JDBC 1.0 compliant). Suggestions for Oracle 8.1.6 and Solaris 2.6 will also be appreciated.
Ozan & Serpil

Hi Jeremy,
Below is meta tags for Turkish
lt & meta http-equiv="Content-Type" content="text/html; charset=windows-1254" / & gt
lt & meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-9" / & gt
lt & meta http-equiv="Content-Language" content="tr" / & gt
I tryed but result is the same.
I think .irpt has no Turkish support.
Thanks.

Similar Messages

Issue with language specific characters combined with AD-Logon to BO platform and client tools

We are using SSO via Win AD to logon to BO-Launchpad. Generally this is working which means for Launch Pad no manual log on is needed. But this is not working for users which have language specific letters in their AD name (e.g. öäüéèê...).
What we have tried up to now:
If the AD-User name is Test-BÖ the log on is working with the user name Test-BO with logon type AD
If the logon Type "SAP" is used than it is possible to use the name Test-BÖ as the username
Generally it is no problem in AD to use language specific letters (which means it is possible to e.g. log on to Windows with the user Test-BÖ)
It is possible to read out the AD attributes from BO side and add them to the user. Which means in the user attributes the AD name Test-BÖ is shown via automatic import from AD. So it's not the problem that the character does not reach BO.
I have opened a ticket concerning that. SAP 1th level support is telling me that this is not a BO problem. They say it is a problem of Tomcat. I don't believe that because the log on with authentification type SAP is working.
I have set up the same combination (AD User Test-BÖ with SAP User Test-BÖ) as a single sign on authentification in SAP BW and there it is working without problems.
Which leads me to the conlusion: It is not a problem of AD. It is something which is connected to the BO platform but only combined with logon type AD because SAP Logon is working with language specific characters.

I have found this article with BO support:
You cannot add a user name or an object name that only differs by a character with a diacritic mark
Basically this means AD stores the country specific letters as a base letter internally. Which means that if you have created a user with a country specific letter in the name you can also logon with the Base letter to Windows.
SAP-GUI and Windows are maybe replacing the country specific letters by the base letter. Due to that SSO is working. BO seems not to be able to do that. Up to now the supporter from BO is telling me that this is not a BO problem.
Seems to be magic that the colleagues of SAP-GUI are able to to it.

Problem with language specific characters on e-mail sending

Hi,
Problem with language specific characters on e-mail sending.
How can it be fixed?
Thanks.

Hi,
try to work on the charecter code set UTF-8 or UTF-16. You can define this in html.
Or encode the charecter using java script.
Hope this may help you.
Deepak!!!

Language specific characters changes when .irpt executed.

Hi,
When i execute .irtp page, language specific characters changes to strange signs.
How can it be solved?
Thanks.

Hi Jeremy,
Below is meta tags for Turkish
lt & meta http-equiv="Content-Type" content="text/html; charset=windows-1254" / & gt
lt & meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-9" / & gt
lt & meta http-equiv="Content-Language" content="tr" / & gt
I tryed but result is the same.
I think .irpt has no Turkish support.
Thanks.

Issues with language-specific characters and Multi Lexer

I want to create a text index with global lexer and different languages. But how to create the index to satisfy all languages?
Oracle EE 10.2.0.4 (UTF8) on Solaris 10
1.) Create global lexer with german as default and czech, turkish as additional languages.
begin
     ctx_ddl.drop_preference('global_lexer');
     ctx_ddl.drop_preference('german_lexer');
     ctx_ddl.drop_preference('turkish_lexer');
     ctx_ddl.drop_preference('czech_lexer');
end;
begin
     ctx_ddl.create_preference('german_lexer','basic_lexer');
     ctx_ddl.create_preference('turkish_lexer','basic_lexer');
     ctx_ddl.create_preference('czech_lexer','basic_lexer');
     ctx_ddl.create_preference('global_lexer', 'multi_lexer');
end;
begin
     ctx_ddl.set_attribute('german_lexer','composite','german');
     ctx_ddl.set_attribute('german_lexer','mixed_case','no');
     ctx_ddl.set_attribute('german_lexer','alternate_spelling','german');
     ctx_ddl.set_attribute('german_lexer','base_letter','yes');
     ctx_ddl.set_attribute('german_lexer','base_letter_type','specific');
     ctx_ddl.set_attribute('german_lexer','printjoins','_');
     ctx_ddl.set_attribute('czech_lexer','mixed_case','no');
     ctx_ddl.set_attribute('czech_lexer','base_letter','yes');
     ctx_ddl.set_attribute('czech_lexer','base_letter_type','specific');
     ctx_ddl.set_attribute('czech_lexer','printjoins','_');
     ctx_ddl.set_attribute('turkish_lexer','mixed_case','no');
     ctx_ddl.set_attribute('turkish_lexer','base_letter','yes');
     ctx_ddl.set_attribute('turkish_lexer','base_letter_type','specific');
     ctx_ddl.set_attribute('turkish_lexer','printjoins','_');
     ctx_ddl.add_sub_lexer('global_lexer', 'default', 'german_lexer');
     ctx_ddl.add_sub_lexer('global_lexer', 'czech',   'czech_lexer',   'CZH');
     ctx_ddl.add_sub_lexer('global_lexer', 'turkish', 'turkish_lexer', 'TRH');
end;
/2.) Create table and insert data
drop table text_search;
create table text_search (
     lang   varchar2(5)
   , name   varchar2(100)
insert into text_search(lang, name) values ('DEH', 'Strauß');
insert into text_search(lang, name) values ('DEH', 'Möllbäck');
insert into text_search(lang, name) values ('TRH', 'Öğem');
insert into text_search(lang, name) values ('TRH', 'Öger');
insert into text_search(lang, name) values ('CZH', 'Tomáš');
insert into text_search(lang, name) values ('CZH', 'Černínová');
commit;3.) The index creation now produces different results depending on the language settings:
-- *Option A)*
alter session set nls_language=german;
drop index i_text_search;
create index i_text_search on text_search (name)
   indextype is ctxsys.context
        parameters ('
                section group CTXSYS.AUTO_SECTION_GROUP
                lexer global_lexer language column lang
                memory 300000000'
select * from dr$i_text_search$I;
-- *Option B)*
alter session set nls_language=turkish;
drop index i_text_search;
create index i_text_search on text_search (name)
   indextype is ctxsys.context
        parameters ('
                section group CTXSYS.AUTO_SECTION_GROUP
                lexer global_lexer language column lang
                memory 300000000'
select * from dr$i_text_search$I;
-- *Option C)*
alter session set nls_language=czech;
drop index i_text_search;
create index i_text_search on text_search (name)
   indextype is ctxsys.context
        parameters ('
                section group CTXSYS.AUTO_SECTION_GROUP
                lexer global_lexer language column lang
                memory 300000000'
select * from dr$i_text_search$I;And now I get different:
Option A)
dr$i_text_search$I with nls_language=german:
STRAUß
STRAUSS
MOLLBACK
OĞEM
OGER
TOMAŠ
ČERNINOVA
Problems, e.g.:
A turkish client now does not find his data (the select returns 0 rows)
alter session set nls_language=turkish;
select * from text_search
where contains (name, 'Öğem') > 0;
Option B)
dr$i_text_search$I with nls_language=turkish:
STRAUß
STRAUSS
MÖLLBACK
ÖĞEM
ÖGER
TOMAŠ
ČERNINOVA
Problems, e.g.:
A czech client now does not find his data (the select returns 0 rows)
alter session set nls_language=czech;
select * from text_search
where contains (name, 'Černínová') > 0;
Option C)
dr$i_text_search$I with nls_language=czech:
STRAUß
STRAUSS
MOLLBACK
OĞEM
OGER
TOMAS
CERNINOVA
Problems, e.g.:
A turkish client now does not find his data (the select returns 0 rows)
alter session set nls_language=turkish;
select * from text_search
where contains (name, 'Öğem') > 0;
----> How can these problems be avoided? What am I doing wrong?

You need to change your base_letter_type from specific to generic. Also, if you are going to use both alternate_spelling and base_letter in your german_lexer, then you might want to set override_base_letter to true. Please see the run of your code below, with those changes applied. The special characters got mangled in my spool file, but hopefully you get the idea.
SCOTT@orcl_11gR2> begin
2           ctx_ddl.drop_preference('global_lexer');
3           ctx_ddl.drop_preference('german_lexer');
4           ctx_ddl.drop_preference('turkish_lexer');
5           ctx_ddl.drop_preference('czech_lexer');
6 end;
7 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> begin
2           ctx_ddl.create_preference('german_lexer','basic_lexer');
3           ctx_ddl.create_preference('turkish_lexer','basic_lexer');
4           ctx_ddl.create_preference('czech_lexer','basic_lexer');
5           ctx_ddl.create_preference('global_lexer', 'multi_lexer');
6 end;
7 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> begin
2           ctx_ddl.set_attribute('german_lexer','composite','german');
3           ctx_ddl.set_attribute('german_lexer','mixed_case','no');
4           ctx_ddl.set_attribute('german_lexer','alternate_spelling','german');
5           ctx_ddl.set_attribute('german_lexer','base_letter','yes');
6           ctx_ddl.set_attribute('german_lexer','base_letter_type','generic');
7           ctx_ddl.set_attribute('german_lexer','override_base_letter', 'true');
8           ctx_ddl.set_attribute('german_lexer','printjoins','_');
9
10           ctx_ddl.set_attribute('czech_lexer','mixed_case','no');
11           ctx_ddl.set_attribute('czech_lexer','base_letter','yes');
12           ctx_ddl.set_attribute('czech_lexer','base_letter_type','generic');
13           ctx_ddl.set_attribute('czech_lexer','printjoins','_');
14
15           ctx_ddl.set_attribute('turkish_lexer','mixed_case','no');
16           ctx_ddl.set_attribute('turkish_lexer','base_letter','yes');
17           ctx_ddl.set_attribute('turkish_lexer','base_letter_type','generic');
18           ctx_ddl.set_attribute('turkish_lexer','printjoins','_');
19
20           ctx_ddl.add_sub_lexer('global_lexer', 'default', 'german_lexer');
21           ctx_ddl.add_sub_lexer('global_lexer', 'czech',   'czech_lexer',   'CZH');
22           ctx_ddl.add_sub_lexer('global_lexer', 'turkish', 'turkish_lexer', 'TRH');
23 end;
24 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> drop table text_search;
Table dropped.
SCOTT@orcl_11gR2> create table text_search (
2        lang      varchar2(5)
3      , name      varchar2(100)
4 );
Table created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('DEH', 'StrauÃŸ');
1 row created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('DEH', 'MÃ¶llbÃ¤ck');
1 row created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('TRH', 'Ã–ÄŸem');
1 row created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('TRH', 'Ã–ger');
1 row created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('CZH', 'TomÃ¡Å¡');
1 row created.
SCOTT@orcl_11gR2> insert into text_search(lang, name) values ('CZH', 'ÄŒernÃnovÃ¡');
1 row created.
SCOTT@orcl_11gR2> commit;
Commit complete.
SCOTT@orcl_11gR2>
SCOTT@orcl_11gR2> -- *Option A)*
SCOTT@orcl_11gR2> alter session set nls_language=german;
Session altered.
SCOTT@orcl_11gR2> drop index i_text_search;
drop index i_text_search
ERROR at line 1:
ORA-01418: Angegebener Index ist nicht vorhanden
SCOTT@orcl_11gR2> create index i_text_search on text_search (name)
2      indextype is ctxsys.context
3           parameters ('
4                section group CTXSYS.AUTO_SECTION_GROUP
5                lexer global_lexer language column lang
6                memory 300000000'
7           );
Index created.
SCOTT@orcl_11gR2> select token_text from dr$i_text_search$I;
TOKEN_TEXT
AYEM
AŒERNA
CK
GER
LLBA
MA
NOVA
STRAUAY
TOMA
9 rows selected.
SCOTT@orcl_11gR2> alter session set nls_language=turkish;
Session altered.
SCOTT@orcl_11gR2> select * from text_search
2 where contains (name, 'Ã–ÄŸem') > 0;
LANG
NAME
TRH
Ã–ÄŸem
1 row selected.
SCOTT@orcl_11gR2>
SCOTT@orcl_11gR2> -- *Option B)*
SCOTT@orcl_11gR2> alter session set nls_language=turkish;
Session altered.
SCOTT@orcl_11gR2> drop index i_text_search;
Index dropped.
SCOTT@orcl_11gR2> create index i_text_search on text_search (name)
2      indextype is ctxsys.context
3           parameters ('
4                section group CTXSYS.AUTO_SECTION_GROUP
5                lexer global_lexer language column lang
6                memory 300000000'
7           );
Index created.
SCOTT@orcl_11gR2> select token_text from dr$i_text_search$I;
TOKEN_TEXT
AYEM
AŒERNA
CK
GER
LLBA
MA
NOVA
STRAUAY
TOMA
9 rows selected.
SCOTT@orcl_11gR2> alter session set nls_language=czech;
Session altered.
SCOTT@orcl_11gR2> select * from text_search
2 where contains (name, 'ÄŒernÃnovÃ¡') > 0;
LANG
NAME
CZH
ÄŒernÃnovÃ¡
1 row selected.
SCOTT@orcl_11gR2>
SCOTT@orcl_11gR2> -- *Option C)*
SCOTT@orcl_11gR2> alter session set nls_language=czech;
Session altered.
SCOTT@orcl_11gR2> drop index i_text_search;
Index dropped.
SCOTT@orcl_11gR2> create index i_text_search on text_search (name)
2      indextype is ctxsys.context
3           parameters ('
4                section group CTXSYS.AUTO_SECTION_GROUP
5                lexer global_lexer language column lang
6                memory 300000000'
7           );
Index created.
SCOTT@orcl_11gR2> select token_text from dr$i_text_search$I;
TOKEN_TEXT
AYEM
AŒERNA
CK
GER
LLBA
MA
NOVA
STRAUAY
TOMA
9 rows selected.
SCOTT@orcl_11gR2> alter session set nls_language=turkish;
Session altered.
SCOTT@orcl_11gR2> select * from text_search
2 where contains (name, 'Ã–ÄŸem') > 0;
LANG
NAME
TRH
Ã–ÄŸem
1 row selected.
SCOTT@orcl_11gR2>

Accessing a specific schema with JDBC

My database has several schemas and I'm trying to access a specific schema using the following code snipet:
Class driverClass = Class("oracle.jdbc.driver.OracleDriver");
Connection jdbcConnection = Drivermanager.getConnection("jdbc:oracle:thin:@datastore:1527:dbname","username","password");
IDatabaseConnection connection = new DatabaseConnection(jdbcConnection);
Is there a way to access schema mike27 on dbname? I keep getting the schema pointed to by the public synonyms.

Hi,
I would think that you have to override the doDML method in ADF BC to then insert/update the values in the scott schema. For this the main schema must have privileges on teh Scott schema to perform the operation
Frank

Language specific characters changes when export as csv

I am using the Save as CSV file property of the grid to show the data in excel. But in CSV some spanish characters like í is getting changed to Ã.
Page is having .irpt extension.
I tried .html as well but it is giving the same error.
Could anyone help me in resolving it.

Hi
This is most probably a character set issue. The problem here is that a CSV file, unlike XML, does not contain a declaration of the character set, so there is uncertainty here.
It is possible that the program you are using to open/import the CSV file is using the wrong character set. There is a tool called the chardet library that may help you determine what the encoding is. See http://stackoverflow.com/questions/508558/what-charset-does-microsoft-excel-use-when-saving-files for these and other details.
Otherwise, if your CSV comes from a query against a database, the database collation may not be aligned with the character data you are storing.
Marc

Language specific characters

Hi!
My reports does not come out with norwegian special characters. My forms seems to be ok though. What system variables need to be set for the reports to be able to show norwegian special characters?
Regards, Morten

You'll need to set your NLS_LANG environment variable / registry setting correcly with the appropriate country, territory and character set (I don't know what these are for Norwegian off the top of my head, but the documentation should cover this). Don't forget that if you're running through the server then you'll need to make sure that this value is also set in the server environment. Finally, make sure that the characters you're trying to display are included in the font that you're using in the report.
Hope this helps,
Danny

Language specific characters problem

My users are to enter text to be stored in an Oracle DB. The insert statement works perfectly, but all Norwegian characters are converted to something unreadable in the insert prosess. How do I get the flex application and runtime environment to not convert these characters?
Doing inserts from other applications to the same DB works for Norwegian characters so this problem seems to be related to VC.
Hoping for help
Henning

I was wrong! When I found that BAPIs doing inserts to SAP tables worked with Norwegian characters, I thought I had found the solution. This is not the case. The same model does not work with Norwegian characters when backported to NW 2004. Nor does my bi_jdbc sql based models reading/writing to the portal db.
Will update if/when solution is found.
Henning

Runtime.exec() with language specific chars (umlauts)

Hello,
my problem is as follows:
I need to run the glimpse search engine from a java application on solaris using JRE 1.3.1 with a search pattern containing special characters.
Glimpse has indexed UTF8 coded XML files that can contain text with language specific characters in different languages (i.e. german umlauts, spanish, chinese). The following code works fine on windows and with JRE 1.2.2 on solaris too:
String sSearchedFreeText = "Tür";
String sEncoding = "UTF8";
// Convert UTF8 search free text
ByteArrayOutputStream osByteArray = new ByteArrayOutputStream();
Writer w = new OutputStreamWriter(osByteArray, sEncoding);
w.write(sSearchedFreeText);
w.close();
// Generate process
String commandString = "glimpse -y -l -i -H /data/glimpseindex -W -L 20 {" + osByteArray.toString() + "}";
Process p = Runtime.getRuntime().exec(commandString);
One of the XML files contains:
<group topic="service-num">
<entry name="id">7059</entry>
<entry name="name">TÃ¼rverkleidung</entry>
</group>
Running the java code with JRE 1.2.2 on solaris i get following correct commandline
glimpse -y -l -i -H /data/glimpseindex -W -L 20 {TÃ¼rverkleidung}
--> glimpse finds correct filenames
Running it with JRE 1.3.1 i get following incorrect commandline
glimpse -y -l -i -H /data/glimpseindex -W -L 20 {T??rverkleidung}
--> glimpse finds nothing
JRE 1.2.2 uses as default charset ISO-8859-1 but JRE 1.3.1 uses ASCII on solaris.
Is it possible to change the default charset for the JVM in solaris environment?
Or is there a way to force encoding used by Runtime.exec() with java code?
Thanks in advance for any hints.
Karsten

osByteArray.toString()Yes, there's a way to force the encoding. You provide it as a parameter to the toString() method.

Problem with "farsi" language . Characters is separate.

android 2.2 . samsung galaxy s i9000 . problem with "farsi" language . Characters is separate. like this :.
. س ل ا م . ا ی ن ج و ر ی .
please help.

fennec-4.0b2.multi.eabi-arm

Copy paste text from pdf exported from Microsoft.Reporting.WinForms.ReportViewer control with Czech specific characters produced box charactex or ?.

Used Visual studio 2012. In our project there is used the Microsoft.Reporting.WinForms.ReportViewer control. In the report handled by the control are TextBoxs with a text with Czech specific characters e.g. (ř, ě, ...) . When exporting the report to pdf,
characters are displayed correctly. However when the text with czech characters in the pdf if copied and placed into the seach box in the pdf document only box characters are displayed. The TextBox in the report use the default font Arial. When the report
is exported to Word, and then the Word document is saved as a pdf document, its ok. Coping a text with Czech charactes in the result pdf document and pasting into the search box displays again Czech characters not box characters.
Also when in the report handled by the ReportViewer control are several Tex Boxes and some of the boxes contains Czech characters and some not, after exporting to a pdf document there is problem with text selection. When in the pdf document I'm trying to
select several paragraphs, some with Czech characters and some without them, selection behaves strangely and jumps from one paragraph to another unexpectedly.

Hi,
did you managed to avoid those squares?
BTW: if any such char. is encountered in a line, the entire line of text is grabbled.
I've tried even the ReportViewer from MSSQL 2014, but got the same problem. When I've tried IL Spy, I found a code, where it is checked if the PDFFont is composite - depending on that a glyph is created. But that still only a guess.
I've tried Telerik's reporting, they have similar problem (beside other), but not with the special characters. They produced scuares for some sequences like: ft, fi, tí.
Please give any info you got.
Until then my advices for you:
a) try JasperReports (seems theyre most advanced, although it is java)
b) Developer express has quiet quality reports - and it seems they got those special chars. right :D
c) I created a ticket and waiting for Telerik's response (but if I had to choose reporting, I vould stick with a) or b)

Problem with language specific letters in Translation Builder editor

Hello,
I'm trying to translate some reports from Slovenian to Croatian using OTB, but as soon as I scroll up or down through translation form some Croatian language specific letters (čćžšđ) either convert to c (čć) or d (đ) or become "unreadable" (šž). The latest (šž) are displayed correctly on the report when strings are exported back to RDF file.
According Troubleshooting section in OTB help I tried to change both base and translation font but with no success.
Any experience, any hint or trick?
Thanks in advance.
Dev6i patch10
RDBMS=Oracle10g
WinXPsp2
NLS_LANG=CROATIAN_CROATIA.EE8MSWIN1250

Naveen,
This is more of a portal problem.
First, you should submit an OSS message to get the <b>best support possible</b> from SAP.
Second, if you don't like that solution, THEN come back and post it on SDN. You will get better answers in the Enterprise Portal forum here on SDN.
Regards,
Greg

How do I type characters with tilde accent marks, specifically an "n"?

How do I type characters with tilde accent marks, specifically an "n"?
I've tried "OPTION N" with no luck... Using a font that supports it...

For example, press Option+N and should see the tilde accent, then press the letter such as n

How do I surface language specific texts in Integrated ITS?

Hello all,
I'm new to both stand alone and integrated ITS and am researching the upgrade process. In our stand alone templates we used htrc files with our html templates to show language specific texts.
Example.
html template code for a field label
`if (i==2) DETAIL-FLABEL[2]= #KAFN end`
htrc name value pair
z_pz01_en.htrc
KAFN Known As First Name
z_pz01_de.htrc
KAFN Bekannt unter dem Vornamen
I see no hint that htrc's can be used in integrated and am not seeing anything in the way of resource based language texts in integrated. I think I've hit every document out there yet, I have a feeling I'm missing something obvious. Your help is appreciated.
Doug

Edgar,
Thanks so much for the detail!
I have run through the steps for manual creation of translations as well as SIAC_UPLOAD of htrc files and have it working and documented. I will add a few more findings here for others who find this post later.
Some of our old htrc files had duplicate keys (probably from original German version). In stand alone ITS the last key in the file was used so this didn't matter. In integrated ITS this matters for 2 reasons.
1 Uploading/Converting htrc files having logged in in English will cause failures if any of the text being entered in the service parameters has characters that arent consistent with the codepage being used for EN. (Ex. back Azureück). Clean up htrc files to use only the language they should contain.
2 Stand alone ITS was forgiving of htrc files containing duplicate keys. Integrated ITS is not. Remove all duplicate keys.
3. This one is obvious but... if parameters have already been entered in another language you may be prompted to confirm you are changing language and there are several prompts along the way. As these prompts will appear in the logon language itu2019s important to eitheru2026
a. Be fluent in all supported languages , oru2026
b. Memorize button and menu positions.
I do have one additional question.
Our old stand alone setup had an alternate corporate "APCI" design that we used...
File system view -
hostDEV_WWWmimesdesigns"apci"webgui as opposed to the out of box
hostDEV_WWWmimesdesignssap_streamlinewebgui I suppose.
I believe this was then referenced in the global services file ~DESIGN="APCI"
I'm starting research to understand if there is an analog to this in the integrated webgui service or precisely what I have to do to accomplish alternate styles for webgui and our Z_services.
Thanks again, points on the way, If I could award more I would.
Doug

Language specific characters with JDBC

Similar Messages

Maybe you are looking for