Page 1 of 1

Export Problem

Posted: Thu Oct 30, 2014 4:56 am
by Dutch
[updated:LAST EDITED ON Oct-30-14 AT 05:07 AM (EST) by ()]Dear Support,____I have problem with export to Excel XLS or CSV. I use Thai charactor.__Export to XLS__=============__1st case charactor ( à¸_ chr(183) -> space )__2nd case charactor ( à¸_ chr(164) -> à¸_ chr(168) )____Export to CSV__=============__1st case charactor ( à¸_ chr(183) -> space )__2nd case NO PROBLEM____Export to RTF__=============__All charactor correctly.____This is my setting in RRW.SRT__SPACEDOT=255____Thank you in advance and waiting for your reply.____Regards,__Dutch__

=> RE: Export Problem

Posted: Thu Oct 30, 2014 5:11 am
by Dutch
The red one (RTF) is correct.__The green one (CSV) is 1 missing charactor__The blue one (XLS) is 1 missing charactor and 1 switch to wrong charactor.__[url=http://postimg.org/image/r8drndo0b/full/][img]http://s1.postimg.org/x9bgkgamn/Export.jpg[/img][/url]__[url=http://postimage.org/]adult picture hosting[/url]

==> RE: Export Problem

Posted: Sat Nov 01, 2014 1:19 am
by cstrasser
We^ll try to setup a test and recreate the problem.

==> RE: Export Problem

Posted: Wed Nov 05, 2014 5:08 pm
by Dan_Levin_(Guest)
In the RRW.srt file (and/or RSW.srt if you use R&R SQL), there is a setting for "DBCHARS=". The settings either DBCHARS=ANSI to tell R&R to use the ANSI character set, or DBCHARS=OEM to have R&R use the characters from code page 437.____ ____The default in these files is DBCHAR=OEM, and that applies even if the line is commented out with the leading comma. My suggestion is that you remove the leading comma and try the DBCHARS=ANSI, since it looks like that is the transformation you are using.______ ____Try the various settings and reply with your results.__

===> RE: Export Problem

Posted: Mon Nov 10, 2014 5:41 am
by Dutch
[updated:LAST EDITED ON Nov-10-14 AT 05:43 AM (EST) by ()]Dear Dan,____1. I try DBCHARS=ANSI and DBCHARS=OEM nothing change, the result the same.__2. I try to change SPACEDOT=250 nothing change.__3. I try to change SRTCHARS=ANSI and SRTCHARS=OEM nothing change.____It still has problem, I found a point. if export with single band line (XLS or CSV or DBF), it got this problem but it will be fine if I export to TXT or RTF (multi band line).____Regards,__Dutch

====> RE: Export Problem

Posted: Fri Nov 28, 2014 9:10 pm
by Dutch
Any help update.

=> RE: Export to MS Excel Problem *Seriously*

Posted: Wed Apr 08, 2015 9:28 am
by Dutch
[updated:LAST EDITED ON Apr-08-15 AT 09:31 AM (EST) by ()]Dear Chris,____I have got this problem with export to XLS or CSV and it can fixed in R&R 10 with editing SPACEDOT=255 in RRW.SRT but it has got this problem again and the RRW.SRT setting is not solving the problem anymore and it has got more problem with chr(164).__How to Fix (Thai charactor)?__1) Charactor Chr(183) is space() *SPACEDOT is not working*__2) Charactor Chr(164) is changed to Chr(168)____Thank you in advance.__Dutch__>Dear Support, __>__>I have problem with export to Excel XLS or CSV. I use Thai __>charactor. __>Export to XLS __>============= __>1st case charactor ( à¸_ chr(183) -> space ) __>2nd case charactor ( à¸_ chr(164) -> à¸_ chr(168) ) __>__>Export to CSV __>============= __>1st case charactor ( à¸_ chr(183) -> space ) __>2nd case NO PROBLEM __>__>Export to RTF __>============= __>All charactor correctly. __>__>This is my setting in RRW.SRT __>SPACEDOT=255 __>__>Thank you in advance and waiting for your reply. __>__>Regards, __>Dutch __

==> RE: Export to MS Excel Problem *Seriously*

Posted: Wed Apr 08, 2015 11:23 pm
by Dutch
Dear Chris and Kathleen,____I test with old version 10+. The problem is the same, the big problem for us. Could you help me to fix this problem please?____Regards,__Dutch