Data Structure & Default Elements
Being in need of a new database system myself, I decided to simply document the process of adding new features to a FileMaker system as it evolves. This is a great way to learn about the ins-n-outs of what goes on when developing a new system. There's a number of things which may or may not make sense when you take a look into how someone else created something. So, why not make videos as the solution progresses.
In this first video, I showcase how I originally started the file and where I should start to plan for a larger solution. There's a bit more needed than simply just throwing some fields into a table. There are also a number of settings and defaults which are created by FileMaker.
This video talks about those default elements, how to deal with them and how to start planning for an easy-to-maintain database solution.
Comments
Reassining fields on a layout
Is there a quick way to reassign all fields on a new layout? My idea is to create an Archive table and an Archive layout. Same as the production one, but I want to move older record there, but still give the ability to the users to browse. It has 100+ fields and individually it's pretty time consuming. Can I use the XML? Any good ideas for that?
Thank you!
Temporarily Renaming TOs Can Help
This answer from the Claris Community should help: https://community.claris.com/en/s/question/0D50H00007XeKCUSA3/is-there-a...
Basically, copy all the layout objects from the original layout, go into Manage Database... and rename the source table Table Occurrence to something like "Temp" and then rename your Archive TO to the original name of the source table TO. Save the changes, navigate to the Archive layout and paste all the layout objects that are sitting on the clipboard. Then go back into Manage Database.... and rename the TOs to their original names.
--
Daniel Farnan
Ignorance is curable, not preventable