>>ok i am accord with you in that bot if you want to change in execution mode de language of your form with out do it manually you need a class that translate all captios for example from spanish to french or englesh to deutch. can i do that? not manually i am talkin a about a control ocx or class like the control that chanche the skin vfpskin.
>
>Any automatic translation would not be trustworthy, nor of high quality.

Even a manual translation isn't quite good. Steven Black's INTL can be put to good use, but one needs to extend it somehow to make it work for various cases that can happen. While individual captions and tooltips may not be a problem, composed messages can be. Consider a message composed as this:

"Couldn't find the "+lcfile+" file."

If we translate the pieces separately, we'd never get the proper translation into many languages. Example in Hungarian and Serbian:

"Nem találtam a "+lcfile+ " fajlot." (notice that "file" translates to "fajl" in nominative case only - we need it to be an object here)

"Nisam našao fajl "+lcFile (because in Serbian it doesn't make sense to say "nnn file", only "file nnn" - and probably so in many other languages).

This means that the messages need to be composed by something that'll have macros in them, and have them translated before the macros expand... something like

lcMsg=translate("Couldn't find the <<lcFile>> file.")
lcMsg=textmerge(lcMsg)

And the translation entries for the entence would contain the same variables. Then it may work.