Give the user the option to not replace script sections with "Code Missing" when importing a Script before the custom functions, layouts, and tables are imported. Give the user the option to not erase the button script action if a Layout is imported before the script is.
Ok, thanks for the feedback.
It would just make it easier if you have a development and production database, so there wouldn't need to be an import priority on object types, or a catch-22 of losing the button actions when importing a layout first or losing the layout references when importing the script first.
I'm not sure I can vote this up, William, simply because we currently are told there are errors and given a detailed import log showing them.
So yes, in a perfect world, it might be nice if FMI protected us from ourselves but it would be much lower priority than several other things here and each of these requests will add to the complexity ( and cost ) of FileMaker thus I cannot rate it up.
I will not rate it down, however, since I might be convinced otherwise and I'm not really against the idea. :-)