Hi All,

I recently posted a question about multi-user & multi-language

issues.

With the help of Ernst i got it working.

One last thing to solve/fix with all the calculated fields

(used as buttons or field labels) when i go into FIND mode they all go blank!!

What can i do not to have this happen? Why is it happening?

I end up with layouts that are in NO language instead of French or English!!

Thanks

--Dan

OK Dan, lets think about this for a moment. When you go into Find mode, you are looking at an empty form. You would not expect to see any data, otherwise you would be overwriting it when you to enter in the find criteria.

Going back and re-reading your previous post, I'm assuming you are using calc fields as labels because of the multi-language usage. What you might have to do is create separate layouts specifically for doing your finds.

HTH, Mike

thanks Mike,

That is what i was afraid of....

I guess I will duplicate the find layouts (1-French, 1- English).

too bad there is no way to tell FM that if the field is a calc field &

allow entry into it has been disable then it's OK to display its contents.

There would be no chance of overwriting data.

--Dan

Or use globals for your finds. They can enter criteria in Browse mode, and then you set the actual fields with the global's data and Perform Find.

Hi everyone,

I'm trying to develop an application where the field labels are in either English or French, depending on the choice of the user. For example, the label could be "Name" or "Nom". I found some tantalizing hints from searching this forum ("using calc fields as labels") but I'm somewhat of a newbie in Filemaker and I'm too sure what they mean. Can someone explain how to do this?

Thanks for the help.

Gordon E.

If the label text is stored in globals instead of calc fields, then they will display correctly in find mode either as a regular global field (no entry allowed, of course) or a merge field. So you could set up your language selection as a script that sets the value of these label globals.

To populate these global fields I would use a separate