FiveTech Software tech support forums

Noviembre 2023 - Enero 2024 =========================== * Nuevo: Para usuarios de Borland: FWH usa ahora el compilador Borland 7.70. Por favor, actualiza tu compilador Borland a esta versión. * Nuevo: Nueva clase TWebView2 que ofres una funcionalidad muy similar a la clase TWebView, pero con la vent...

November 2023 - January 2024 ============================ * New: For Borland users: FWH uses now bcc 7.70. Please update your bcc to this version. * New: Class TWebView2 offers a very similar functionality to Class TWebView but does not need to use any DLL. It is a work in development but you can al...

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 while using DrXlsx. ok i will wait and try "your" ...

Thanks again. Here is the comparison between 1. Direct OEM view from Command Prompt using Harbour's DBEDIT. 2. FWH XBrowse of the same DBF in ANSI, just by using one flag oBrw:OemAnsi := .t. 3. Excel as exported using DrXlsx by the new FWH interface to this library All look identical https://ima...

Jimmy wrote:hi,

have send you a new Email with Link

Thanks.
This will help me to learn.

hi,

have send you a new Email with Link

to say it again : i need "read" from existing DBF, NOT "made" it from CODE Yes. This is what we are very much interested to support you with. We request you to please send a few thousand records from the existing dbf, instead of a created dbf (say with chr(1) to chr(255)) You ma...

hi, If you see my earlier samples, I created OEM dbf with Umlauts and showed exporting them to say it again : i need "read" from existing DBF, NOT "made" it from CODE i talk about DBF made under Cl*pper OEM / DOS which many Xbase++ User have as OEM is default this Way Xbase++ Use...

as long Sign come not from DBF, made in OEM Environment , it is not the Problem that i mean

It works the same way even if is from oem dbf.
If you see my earlier samples, I created OEM dbf with Umlauts and showed exporting them

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 OEM dbf with a few thousan...

hi, This is the code for 255-32 records as long Sign come not from DBF, made in OEM 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...

Size < 1 Kb, 255-32 Records, 1 x FIELD RECNO() -> CHR(x) This is the code for 255-32 records function Chars33to255()   local oXlsx   local cFile := "chars33to255.xlsx"   local n,na, c, cx   ? "Start"   oXlsx := TDrX...

German does not use "accent" Sign

I am asking out of ignorance.
Are these not German characters?

õòóôûúùâáàãêéèÃÁÀ

I typed these characters using Google Virtual Keyboard for German Language

have send you a Email with Link to my Online-Web-Space where i have upload "DE_OEM.ZIP"

I did not receive it yet.

email:
nageswaragunupudi [@] gmail [dot] com

hi, May I ask about your oem.dbf? have send you a Email with Link to my Online-Web-Space where i have upload "DE_OEM.ZIP" 1. Does this code display the text correctly or correctly in most of the cases? XBROWSER "name.dbf" SETUP ( oBrw:lOemAnsi := .t. ) or USE <name.dbf...