Charles,

>Using my English language vfp6 development system, I built my exe, and installed it on a target machine running an English-language version of Windows. The program installs both vfp6renu.dll and vfp6rdeu.dll.
The first thing I'ld check is running on a german set OS. There's even some logic behind it: anybody wishing to use your german version probably runs with his OS set to german defaults <g>.

>I cannot get the -L run-time switch to make vfp6 use vfp6rdeu.dll on the target machine. At least, I don't think vfp6rdeu is being used.
cdow() should help you find out.

>I normally start the exe via a short-cut icon on the desktop.
>I added " -LVFP6RDEU.DLL" (without the ") after the exe name in the target field of the short-cut properties window.
>
>I also tried starting the exe from the command line, using the -L switch.
Umpfh, haven't kept up with all the changes in fox and OS (anybody loves the registry ?) in that area. Get a few boxes to test concurrently, read the docs and try, try...

>I have tried this on Win98SE2 and WinXP.
>I installed vfp6rdeu.dll in both the windows system directory, and the directory containing the vfp6 exe.
>In all cases, the program still displays English text on command buttons in dialog boxes generated from messagebox commands.

Here I'm betting on the OS setting, since API functions are used.

One warning: Since the german setting of point and separator is opposite to nearly the rest of the world, this can be a hard to find source of trouble. This is also influenced by the windows regional setting and can be murder on reading csv and ascii files. It still bites me sometimes, even if I am used to working in a german setting.

Minimize the permutations of OS and runtime: Otherwise support could be more work than expected.

HTH

thomas