The NAMES of things

Ok, so I just cleaned up my previously very spaghetti-like RG to a
very orderly AnchorBouy-like design, with out changing any
relationships. Now that I have done this, I can glaringly see the
inconsistencies in my naming conventions.

So I want to start renaming things, BUT before I do I just want to
confirm that if I rename ANYTHING in filemaker 9, that the new name
propagates throughout the application. This is a single file solution.

Are there any elements in the FMP9 that do not propagate their name
changes?

Darren

Re: The NAMES of things

On Nov 2, 5:13 pm, Darren wrote:

> Are there any elements in the FMP9 that do not propagate their name
> changes?

Yes:

Any quoted reference to an object, like a scripted:

if get(currentlayoutname) = "myLayout" then...

won't get updated. Obviously if you change the name of "myLayout", the
quoted string won't be updated. Any of the get functions that retrieve
name information are likely areas of concern. The get function itself
will work just fine, but what you do with those retrieved names may
break.

Likewise "Go To Layout name by calculation" or "Select Window by name"
will break.

Anything used with in an Evaluate() function can break. (usually table
occurences and/or field names).

Also don't forget "named" fm objects that are named using the View-
>Object Info box, and accessed via script steps like Go To Object
(name). To my knowledge changing those names never propogate anywhere,
and all references to a name have to be manually kept track of.

That said, most well designed and implemented databases should not
rely much on any of the above, and should update quite nicely. But
there definately are some gotchas.