FiveTech Software tech support forums

hi, thx for testing German "Umlaute" i do not have Problem with XBROWSE, i do have Problem with DrXlsx LIB When the new version FWH2309 is released, you do not need to any utf8 conversions on your own. FWH will do this conversion ...

... may use https://wetransfer.com/. Please send the download link to me and also Mr.Antonio. "only" DrXlsx LIB need UTF8 where German "Umlaute" fail WHEN it come from German OEM DBF The version of FWH to be released, will come with an interface to DrXlsx lib. Conversion of AnsiToUtf8 ...

... ( not all Language ) --- "normal" i just need to change CODEPAGE from "DEWIN" to "DE850" to display German "Umlaute" under harbour than also "input" under harbour is right when look using Xbase++ App "only" DrXlsx LIB need UTF8 where ...

as i say these OEM DBF was made by Cl*pper App, using NTX, where i have OEM Sign with German "Umlaute" as Xbase++ default use OEM it is a Problem of all Xbase++ User when want to change to Fivewin (and still use Xbase++ OEM App) If you can share such a real life ...

... Environment , it is not the Problem that i mean as i say these OEM DBF was made by Cl*pper App, using NTX, where i have OEM Sign with German "Umlaute" as Xbase++ default use OEM it is a Problem of all Xbase++ User when want to change to Fivewin (and still use Xbase++ OEM App) i can change ...

... SETUP ( oBrw:lOemAnsi := .t.  ) will test it Does changing Codepages make much difference? when Codepage is wrong German "Umlaute" does not Display / Print it are those 7 "Umlaute" only ( German does not use "accent" Sign ) 2. How large is the dbf? ...

i like to get a working Excel Sheet with German "Umlaute" using DrXlsx Suggested: OEM -> ANSI -> UTF8 For ansi to utf8 UTF16toUTF8( strToWide( cAnsi ) ) So we can use: UTF16toUTF8( strToWide( UML_OEMTOANSI( ...

... cCodepage EXCLUSIVE now please try to "export" to Excel using DrXlsx, NOT XBROWSE i like to get a working Excel Sheet with German "Umlaute" using DrXlsx --- when you ask me for STRTOHEX() i got xValue = "„" STRTOHEX(xValue) = "84" ASC(xValue) = 132 xValue ...

hi, this i got when have use DBU and fill it with German Umlaute xValue = "ä" STRTOHEX(xValue) = "84" ASC(xValue) = 132 xValue = "ö" STRTOHEX(xValue) = "94" ASC(xValue) = 148 xValue = "ü" STRTOHEX(xValue) ...

hi, That is nice. So are you able to finally solve the conversion issue? Yes, after STRTRAN() "Umlaute" and use this CODE to "check" Sign FUNCTION CheckValue( xValue, lNoCheck )LOCAL cRet     := ""LOCAL aSign    := "abcdefghijklmnopqrstuvwxyz ...

... also APP Speed decrease using 32 Bit App so also XLSwriter 64 Bit is 500 % faster :!: --- Epilogue : Benefit ADO : work under 32 Bit App. no "Umlaute" Problem using OEM DBF Limitation : Speed like ActiveX Benefit XLSwriter : SPEED Limitation : need UFT8 else it "crash" not sure ...

... also APP Speed decrease using 32 Bit App so also XLSwriter 64 Bit is 500 % faster :!: --- Epilogue : Benefit ADO : work under 32 Bit App. no "Umlaute" Problem using OEM DBF Limitation : Speed like ActiveX Benefit XLSwriter : SPEED Limitation : need UFT8 else it "crash" not sure ...

... (40 Year old) DBF, start with 7-Bit C/PM under Dbase ]} over. Dbase III+. Cli*pper, Xbase++, HMG and now Fivewin these DBF (still) have OEM "Umlaute" not ANSI "Umlaute" but there is no OEMtoUTF8() Function in FiveWin, or :idea: i have try these OEM   // OEM   cText := STRTRAN( ...

... that i got : ISOEM() when have "äöü ÄÖÜ" ISANSI() when have "ß" i never get IsUTF8 but get a lot "ELSE" (no "Umlaute") so what Type is it when got "ELSE" :?: --- DBF was open with CODEPAGE, hb_cdpSelect() "DE850" / "DEWIN" ...

hi,

does it work with OEM DBF and German "Umlaute"