Text Field Defaults

[goldie]

I have been using FM for many years, but only recently have I been having this problem. For simplicity sake, let's say I have one table with two layouts. Layout One has been set up with name and address fields in Optima 14. Layout Two has the same fields but set up in Optima 12. Data entered into Layout One in Optima 14 appears as Optima 14 (not 12) when viewing Layout 2.

I don't know whether I have changed preferences, or whether this inability to retain the field text properties when going from layout to layout is something to do with upgrading to FMP7.

Is there something I should be trying other than reloading the FMP7 software?

Any suggestions very welcome.

[Raybaudi]

For even more simplicity, can you put the same field in the same layout and set, while in layout mode, Optima 14 for the first occurrence and Optima 12 for the second ?

Now, in browse mode, what you see into those fields, if you type something ?

[Lee Smith]

Are you using the current version, 7.0v3.

[goldie]

Thanks for the input on my problem with fonts not holding their default settings going from layout to layout in FM7.03

I have done some more experimenting and the problem does not exist when I set up a new FM file. Nor does it happen when I create new layouts using the create new layout/report "wizard."

The problem remains with existing layouts - I may specify that a layout has a text field in 12 point, but if the same field on another layout is in 10 point, it stays in 10 point when I go to the layout where the field is specified as 12 point.

I appreciate the help so far.

[Lee Smith]

Is this a file you created in a version prior to 7 and then "Converted"?

[goldie]

Yes Lee. Converted to v7 18 months or so ago.

Some of the fields even go back to v3 - it may just be that these are the ones causing the problem.

Seems like you are on to something, but what to do?

Thanks for your interest

[goldie]

One further bit of info for the kind folks interested in my problem of text not taking on the font characteristics specified for that field on a particular layout.

On layout one, the name field is specified as optima 12/black/plain.

On layout two, the same name field is specified as helvetica 14/blue/bold.

Go from layout one to layout two in browse mode and optima12/black/plain becomes optima/12/blue/bold.

So all font characteristics except colour are changed in browse mode when going from layout one to layout two.

The problem remains when changing font characteristics in browse mode.

[Lee Smith]

Without seeing the files, I can only speculate on what is happening.

To begin with, the recommended way to migrate your older files to v7 is CREATE them in v7, and then import your data.

The problem you were describing sounded like either a bad font, or a possible corrupted file.

I have read that v7 has a better way in dealing with file corruption, and will sometimes open a file that was unrecoverable in earlier versions. Again, though it was then suggested that you redo your filess in v7, and import the data to the NEW files.

Fonts come to mind because, they have often been the problem behind things on the Macintosh, and because FileMaker was forgiving about fonts in the older versions, but has now made it required to have the fonts Active.

Lee

[comment]

This is the first time you have mentioned "changing font characteristics in browse mode". Filemaker 7 has the option to store styled text. Any styling attributes styled text may have are stored as part of the DATA, and they override the settings of a field in Layout mode.

When you're changing font characteristics in Browse mode, you're creating styled text (and modifying your data).

[Ender]

To remove the formatting that's tied to the data, you can use:

Evaluate(Quote(Field))

either in an auto-enter calc on the field to automatically reset it to the layout's default upon data entry, or in a Replace Field Contents calc for a one-time fix.

[goldie]

Thanks again to all for the responses to my query about text not holding to the default set for the field in layout mode.

Veteran mentions about changing the font in browse mode.

I have now done a sweep of my file to make sure all fonts in browse mode are the same as specified in layout mode. The problem remains - in browse mode, a field in Layout A appears in Optima 12 (as specified for the field in layout mode) but still appears as Optima 12 on a layout where the default is set to Optima 10.

I'll follow up on some of the more drastic measures already suggested.

I appreciate the interest.

[comment]

Can you post a demo?

[goldie]

Just a follow up on my concern about text fields not retaining their specified characteristics as I moved from one layout to another.

1. Although I have never noticed it happening before (and I'm going back to FMP3 days), text characteristics set in Browse mode do override characteristics set in layout mode on all layouts - as was pointed out by one of our colleagues. As a by-the-way, all characteristics except colour were over-ridden.

2. Writing a script to change, in Browse mode, the font characteristics of a text field contents back to their specification as set in layout mode did not solve the problem.

3. Writing a script which cut the contents of a field, going to another field, then pasting without style into the original field did work.

4. I need to pay attention to the option/command/paste function if I am pasting text into FMP.

Thanks again for all the input I got on this one.