>>I also have an English/Spanish app using INTL. I would be interested to hear how your INTL team handled forms. Using INTL to translate strings on the fly is one thing, but rearranging objects on forms is quite another. I started out keeping 2 sets of forms because the object positions were just to drastically different. Then I had a brain storm, and I only need 1 set of forms regardless of the language, and all translation occurs at runtime.
>
>Some of the forms have been subclassed for each language. In other cases, enough space has been left and buttons sized so that the text will fit.

I thought about that, but I still did not want the PITA of maintaining different language forms [1 record per object]. I finally just created a new table to store the properties, including the translated caption, for all the objects on the form for every form. Like INTL, this table has a memo field for each language that I use and can easily add additional languages. In the Init of by base form class is where I placed the code to process these properties.

I then created a builder where I could right-click on any object so I could set these properties until the object is where I need it for any language.