>While searching from the web I have found a similar solution for ASP web pages that could be adapted to Foxpro. Using include file which defines the strings that need to be localized. Where you include the right file for your chosen language.
>
>I will try this method to see how it fares.

You will have to decide whether you want to compile separate executables, or a single executable, with the texts separately.

In the first case, you can use include files; execution will be somewhat faster, but I don't know how significant this is.

In the second case, you have to read the texts from some external file, like a table or a text-file. Well, it might be a file internal to the executable, but an external file gives the user additional localization options, like, adding support for the Quechua language, which you hadn't originally planned.

I liked the way the localization was done in the Opera browser, and adapted it, more or less: in Opera, you have a main download, currently about 16 MB, I think, and then you can download the language files (text-files), for slightly over 100 KB apiece. Being a text-file makes it especially easy for the user to do any corrections, or add additional languages.

On the other hand, having items in a more structured form (i.e., a database) makes it easier to upgrade to a later version. You might also combine the two approaches, i.e., have procedures that convert from DBF to text, and vice-versa.