🚀 go-pugleaf

What are your NT Country settings?
Tom

Jens Vestergaard wrote:

> This is beyond me:
> I'm using VB Resource Editor to create two string tables for my app. One (the first column) is Danish (Dansk), which is the language of my Windows 95, the other column is named "Neutral" having English strings. The idea being that when run on a non-Danish Win95 version the English string table would be used. This is how I read the documentation for the Resource Editor.
>
> So far so good. When I run the app in the VB5 design environment the Danish string table is used, no problem, but after compilation, when run from the EXE-file, the Neutral (English) string table appears!
>
> I don't get it.... Do you? In that case, thank you for an explanation! :-)
>
> --
> Jens Vestergaard
> http://www.railsoft.dk
> Reply: jv at railsoft.dk
> dk-online is for spam :-)

Douglas Marquardt wrote:
>Hi Jens:
>The *First* string table is the *default* string table.  Because you have
>Danish as the first string table, it will load on any machine where none of
>your string table LCIDs match.  You will have to make the Neutral string
>table the first one to be the default -- here is the excerpt from the Res
>Editor help file:
><snip>


Thanks... BUT:

Yes, I did read that ... and that's what made me use the multiple string table setup in the first place.

It doesn't seem to be true on Win95, however. In the EXE-file my Danish Win95 does NOT find the string table which is BOTH the *First* AND the one marked "Danish" - instead it jumps to the *Second* table. And this is true whatever I call the *Second*: Neutral, Neutral(Sys Default) or English. The strange thing is that it chooses Danish in the VB-environment....

And yes - I do have Danish as language-selection.

I still don't get it.

Tom Clement skrev i meddelelsen <34C68164.E94DEBD6@remove.this.MOSAIX.COM>...
>What are your NT Country settings?
>Tom
>

I'm not using NT, but Win95 - and I'm using all-Danish settings! But your question is probably relevant since another good reader of these ngs has suggested the same - for NT. There seems to be serious differences between NT and 95 on this matter. Or?

Jens


>Jens Vestergaard wrote:
>
>> This is beyond me:
>> I'm using VB Resource Editor to create two string tables for my app. One (the first column) is Danish (Dansk), which is the language of my Windows 95, the other column is named "Neutral" having English strings. The idea being that when run on a non-Danish Win95 version the English string table would be used. This is how I read the documentation for the Resource Editor.
>>
>> So far so good. When I run the app in the VB5 design environment the Danish string table is used, no problem, but after compilation, when run from the EXE-file, the Neutral (English) string table appears!
>>
>> I don't get it.... Do you? In that case, thank you for an explanation! :-)
>>
>> --
>> Jens Vestergaard
>> http://www.railsoft.dk
>> Reply: jv at railsoft.dk
>> dk-online is for spam :-)
>
>
>

Hi Jens:

>I'm using VB Resource Editor to create two string tables for my app.
>One (the first column) is Danish (Dansk), which is the language of my
>Windows 95, the other column is named "Neutral" having English strings.
>The idea being that when run on a non-Danish Win95 version the English
>string table would be used. This is how I read the documentation for the
Resource Editor.


The *First* string table is the *default* string table.  Because you have
Danish as the first string table, it will load on any machine where none of
your string table LCIDs match.  You will have to make the Neutral string
table the first one to be the default -- here is the excerpt from the Res
Editor help file:

<snip>
A string table will automatically be selected at run-time based on the LCID
of the system; if a match isn�t found the system will load the first string
table in the resource file
<snip>

Hope this helps,

Doug.

Hi Jens:

I did some more investigation on this... it appears the problem is with
Win95 OSR2 -- is that what you are using?

As far as I can tell (based on MSDN docs, talking to VB tech support, etc)
that VB does not support ResourceLocal while working within the IDE (has to
do with the fact that Win95 does not support SetThreadLocale like NT does);
however it should work in the compiled exe.   In all my testing, this is the
way it worked on all machines, except those with OSR2 installed -- so the
problem appears to be with that version of Win95.

If I get any more info I will post it.

Doug.