Well, I have a db called Client. Then I designed all the pretty layouts, etc. I added all the fields, the StatusBar calcs, Layouts: Menu, Lists, Portals, finds, global containers for buttons, etc. and I was getting ready to add my 'wish' items such as Undo features, User Preferences to eliminate deletes, Log tracking field by field. But wait ...

I want consistency through my system. I want these things in EVERY db that Users will interact with. Geez, I was getting tired just thinking about repeating this process through the next 11 dbs (not to mention 5-20 layouts each.

My question is: Is it acceptable practice it built it backwards (so to speak)? Maybe create one 'dream machine' with everything automated (at least the shell), copy it, THEN add the specific fields? I know there will be adjustments to Portals, placing fields, etc. and this may not work for scripts which apply to specific fields (but for Windows Views, etc it might). It sounds easier to me. Any suggestions on a full revamp process and am I making a mistake?

Not sure I followed that last part of your query, but I largely have done the same thing as you. I designed my relational system, whipping up the fields and relationships of about a dozen files. Then I started building the layouts... at which point I realized how anemic the built-in stuff is... realized how little support there was for making common changes to many files... realized how impossible it is to cut n paste, let alone setup macros and such...

So, I stopped that work, and focused on building a single template DB that had all the basic stuff that I wanted in every file. I played with it, manipulated it, grew it, paid to have it reviewed by a FM expert. I have all kinds of cool features (see the Sample Files for an intermediate state of that template).

Now, with that template fairly solid, I am rebuilding the relational design using the Template. Essentially, I just need to follow the formula for how to add a field and then follow one of the three basic layout patterns that I created for each needed layout.

However, knowing that I would find ways to further improve the template, I am going file-by-file, trying to get each file fairly thoroughly implemented. That way I improve the template while I still only have 3-6 files. And even those fixups are DAMNED tedious. Several times, about the time I've retyped something for the 2-dozenth time, I'll realize some way to restructure things to make it much easier to maintain.

Now I am fine-tuning the first set of six relational files. When I have them solid, I am going to go ahead and import data into them and get some users using the system with partial functionality. The intent being to find as many issues as I can so that I can fix them consistently across those six files, before those six become three-times that!

Then (probably mid next week) I'll move onto those other files... hopefully I'll have the template real solid by then. Even with six files, mods are horrendous.

Did that answer your question? (At least in terms of one person's similar conclusions.)

I really appreciate your response. I wanted to check with the Forum, because I didn't want to find out later, "Oh, no don't do that! You will have this problem or that problem." I realize it won't be perfect across the board and that each module with have some unique functionalities, but I'm focusing on consistency to make the system 'old shoe' comfortable for our Users. I KNOW bad design -- it makes your day drag and the world appear bleak indeed. I'm starting a list of things, such as: Font (cross-platform consistency), colors (visual-ease as well as how it appears on different configurations & the web). I have copies of all the Forums posts regarding Windows handling, etc.

I have a chance to pre-plan this one ... I want it right, and I don't want to spend hundreds of hours, as you say, re-entering the same formulas. Please everyone, more thoughts? This will be cross-platform, MAC/Win98 & eventually published to the web. Can ya'all help me come up with "what every User-accessed db should have?" I'd be very appreciative!

Makeing a template is a very good idea. Like kennedy said, make sure you have them right before you use it as a base for a large system.

Databasepros.com and layoutmode.com have some templetes (the latter or free) and I'm attaching my personal template I use for starters (which has some rough edges) to this message.

AquaTemplate14.fp5.zip

Thank you so much! I've downloaded everything from both those sources and have borrowed (stolen) everything I can. Thank you for sharing your template with me. I am starting a document listing everything that should be standard in all dbs - such as Startup & Shutdown scripts. Lean, mean & standardized ... that's what I'm after! It appears that there is 50 ways to script something, I've seen scripts a page long and the same script 3 lines!! I was the most efficient scripts. If you wanted to send me (or attach) your 'perfect' db ideas, I'd LOVE it! Multi-level undo on EVERY db, auto row highlight on EVERY list ... consistent Unique Primary ID's - stuff like that! Bless ya ... and everyone that's helping me pull this together!! Everyone is welcome to email me at [email protected] with ANYTHING they think is a good idea!

Another important consideration is security. If different users will need different levels of access, that should be considered at the outset.

I forgot about that one I just added it to my list Thank you SO much! This is exactly what I need to hear. Thanks Bob!

This all of course begs the question "why the hell isn't this support more robust in Filemaker to begin with. I've been using it since 1.0 or 2.0, I can't remember which now. But the layout tools really haven't changed.

Filemaker really needs some sort of style sheet develoment tool ala any good html editor.

I also would love to see an "aqua" or "XP" style ability. Basically I'd like the ability to add fields and tell them which aqua or xp interface element to emulate. This would save a lot of time in development and give FM databases a consistent look with regular stand alone apps.

Meanwhile I'll keep using format painter, and cursing a lot.