Doing two things speeded FM12 enough to allow me to continue using it for now:
1. Minimize use of conditional formatting. Conditional formatting uses much more CPU power, slowing Filemaker renders down - particularly in list view.
2. Converting every field in the old engraved border style to the new solid 1px border with left and top sides selected. This prevents Filemaker from using two methods to render a layout - only the newer method is needed.
In retrospect would this have been easier to do while the file was still in V11 ?
Marianco, useful observation!. I have created a new discussion specifically for this topic: Fields drawing speed in FM12 depending on styles?
usbc, I think it's easier to remove the styles in FM12 but if you prefer to maintain all styles and just remove the engraved border then it may be easier in FM11.
In the Utopian world that we DON'T live in, if I where designing a LARGE system, I would do the following:
NO calculation fields AT ALL, no LOOKUPS, no auto-enter calcs and NO script triggers, NO conditional formatting and minimal PLUGINS (I'd really only need something like Base Elements plugins), layouts are as consisent as possible and scripting is more generic (one script for a commonly performed action). I would perhaps even go as far as to say, the only goto related record I'd use is the goto related records based on found set. (pretty radical, huh?)
All of which are doable...
Which defeat totally the point of a relational database...
Note really, there would still be relationships, I never suggested removing those. My 'ideals' are to improve performance, not re-invent the wheel ;-)