dBase Language drivers

Ran into a new problem with an old application and traced it to the byte 29 in
the table header. We use a table created in another app, and this month the old,
standard app could not open the table and crashed the system. The error message
mentioned the language driver, and after some time I discovered that byte 29 is
now 02, whereas it previously was 57. I discovered that the table in question
was created, this time, with the external app running under dBase 2K; I think it
may have been usual to run it under dBase 5.7, but I'm not sure of that.

On Fri, 08 Feb 2008 11:28:35 -0500, in dbase.install-config, 
Subject: dBase Language drivers, 
Message-ID: <JW#In#maIHA.1752@news-server>,  
Bob Newman <rnewman@mindspring.com> wrote:

>Ran into a new problem with an old application and traced it to the byte 29
in the table header. We use a table created in another app, and this month the
old, standard app could not open the table and crashed the system. The error
message mentioned the language driver, and after some time I discovered that
byte 29 is now 02, whereas it previously was 57. I discovered that the table in
question was created, this time, with the external app running under dBase 2K; I
think it may have been usual to run it under dBase 5.7, but I'm not sure of
that.
>
>During this detective work I discovered that my local vdb57 was running with
the dBASE ENU cp437 language driver, which puts a 1b in byte 29, and that
"ascii"ANSI is the 57, and that WEurope ANSI is 58. What is 02? Which
is the proper one for us to run? TIA

The language driver ID 0x02 is Paradox 'intl'.

The proper language ID to use? It depends mainly upon the language you use in
the application. For
example if you live in Taiwan it is probably not practical to use a driver which
works with the
Icelandic alphabet. On the on the other hand, if you need the graphical
characters in cp437 you
should not select 'WEurope' ANSI.

You really need to give a little more information about the application and
where it is going to be
used.

It's an app written in 5.7, but uses tables that may get created/manipulated in
dB2k, dBasePlus, and FoxPro. My local copy of VdB defaulted to the cp437 and has
been that for years. My dB+ defaulted to "ascii"ANSI, and I have never
changed it.

Ivar B. Jessen Wrote:

> On Fri, 08 Feb 2008 11:28:35 -0500, in dbase.install-config, 
> Subject: dBase Language drivers, 
> Message-ID: <JW#In#maIHA.1752@news-server>,  
> Bob Newman <rnewman@mindspring.com> wrote:
> 
> >Ran into a new problem with an old application and traced it to the
byte 29 in the table header. We use a table created in another app, and this
month the old, standard app could not open the table and crashed the system. The
error message mentioned the language driver, and after some time I discovered
that byte 29 is now 02, whereas it previously was 57. I discovered that the
table in question was created, this time, with the external app running under
dBase 2K; I think it may have been usual to run it under dBase 5.7, but I'm not
sure of that.
> >
> >During this detective work I discovered that my local vdb57 was running
with the dBASE ENU cp437 language driver, which puts a 1b in byte 29, and that
"ascii"ANSI is the 57, and that WEurope ANSI is 58. What is 02? Which
is the proper one for us to run? TIA
> 
> The language driver ID 0x02 is Paradox 'intl'.
> 
> The proper language ID to use? It depends mainly upon the language you use
in the application. For
> example if you live in Taiwan it is probably not practical to use a driver
which works with the
> Icelandic alphabet. On the on the other hand, if you need the graphical
characters in cp437 you
> should not select 'WEurope' ANSI.
> 
> You really need to give a little more information about the application and
where it is going to be
> used.
> 
> 
> Ivar B. Jessen