Tracking down where a font is used?

[Ward]

When I open one of my databases on my Mac OS X development system, FontAgent momentarily reports it's activating a Helvetica Narrow font, which I have not intentionally used in this or any other FileMaker database.

Since I will be deploying this database on other Mac and Windows systems, I'd like to track down and eliminate the Helvetica Narrow reference. I'm hopeful there's a way to do this short of checking the font on every field in 8 layouts.

Suggestions?

-- Ward

[Lee Smith]

Hi Ward,

I had this happen to me a few years back. and it was also with Helvetica Narrow. I didn't develop the file, so I'm not sure what fonts were actually used. And, it wasn't too long after that the file crash and burned. I did do a few things, and I can't remember if I ever fixed it or not. But I didn't know than what I know now either.

I would start by saving a NO RECORD CLONE of the file and see what happens when you open it. No complaints, than I would bet that the errant font is in the data. If it complains, then the errant font is in the fields.

If it is the data, I would just loop through the files with a Replace Script. If it is in the Clone, You could try selecting all of the fields in each layout and replacing them with a different font, but I would consider the file corrupted, and take the opportunity to recreate the file, and then import your data into it.

HTH

Lee

[Lee Smith]

See the post by Fenton, This was what I was trying to say, but Jimmy Jones does a better job.

http://www.fmforums.com/threads/showflat.php?Cat=0&Number=164191

HTH

Lee

[Fenton]

I'm no kind of font expert (I only use about 5 total :-). But I remember there being quite a bit of funkiness about fonts when moving from OS 9 to OS X, much of it to do with Helvetica, which can have several copies on your machine. So it may be that you're suffering from some of that. But maybe not. As Lee says, you can try changing the fonts on the layouts and "neutralize" the fonts in the data. Remember that setting a field to itself does not strip fonts in 7. You can use the calculation:

Evaluate ( Quote ( field ) )

[LaRetta]

Remember that setting a field to itself does not strip fonts in 7

Not at the layout level, no. Because in vs. 7, font format attaches to the field (which is actually good). Ward, also be sure that font isn't listed in your Edit > Preferences > Fonts list.

But about neutralizing fonts ... Field Definitions ignore the 'font memory' and you can reformat the data throughout an entire structure all without leaving Define Fields. Change standard text field to calculation (leave indexing as it defaults - do not click 'Unstored') - or format multiple fields to calculation at one time. Enter your preferred font or format in the calc boxes, such as: TextSize(TextFont(TextStyleAdd(text; "plain"); "Verdana"); 10). I copy/paste into several field calcs in a whack. Exit Define Fields then go back in and change it/them back to standard fields again. I've reformatted entire import multiple field data this way.

Tested - Reformatted 500,000 records (25-character Auth Net text field):

Loop script Freeze Window[], Go To Layout[Form], Go To Field[anyField], Go To Recorc[First], Set Field[] yada yada ... 26 minutes.

Omit Record script (no Go To Field [Next] required) ... 18 minutes

Replace Contents ... 10 minutes

Field Definition (above) ... 3 minutes

For the first time ever, my data normalization and migration through 950,000 (total solution) records has actually become easy. And it is usually the Developer that handles these types of cleanups anyway. I use it quite often now.

Using Field Definitions to change all 500,000 LineItems records (whether their font data was incorrect or not) was even quicker than performing a Find for only funky data and then correcting just them. My 'beast' (LineItems) is finally beginning to purrrrr!

LaRetta