June 23, 200223 yr Newbies I have a database with 3 different tabbed layouts.....I want each layout to be its own record with its own fields in it. How do I set this up. I can't figure it out.........Thanks for your help and suggestions in advance.
June 23, 200223 yr A record is a collection of data stored in fields. A layout is a way of presenting the data in any given record, i.e. record information doesn't change from one layout to the next -- just the way that information is presented. When you create or edit a layout, you can add or remove any fields you like from the layout without affecting the data stored in the record. I hope this helps you out.
June 23, 200223 yr Author Newbies Thanks for the info........ummm I have another question then.......right now I have different fields in all 3 layouts.....but when I try to add a new record to one layout...it will add a record to all three layouts......and the same goes when I delete a record....it will remove a record from all three layouts........is there anyway for the layouts to act as their own individual entity....so If i remove a record from layout 1....it will not remove records from layout 2 and 3...........
June 23, 200223 yr Maybe someone else here has a better way of explaining this than I. What it comes down to is that we are talking about two very different parts of FileMaker. A record stores one instance of information in one or more fields. A single business card is an example of one "record" with several "fields": Name, Company, Address, Phone Number, etc. A layout is just a way of presenting data to the user. It has no effect on the data stored in the database. You can make one layout with every single field in the database on it and another layout with no fields whatsoever; the information in any given record will be the same whether you are looking at the first layout or the second. So, if you delete a record, it will be deleted no matter what layout you are looking at. I'm sorry, I can't help you much more than that. If you can be more specific with what you are trying to do, I'm sure I or someone else can offer a better answer.
June 24, 200223 yr What you want is another file, not another layout! Most sophisticated databases have a number of files... for example, a store database system might have a clients database, an invoices database, and a products database. They all relate to eachother through "key fields", such as the client number or the product number. This is called a "relationship". You definately do not want to be storing "different" types of information in one file... in other words... don't create different layouts for totally different types of information, use them only to change the presentation of information in one database. Hope this helps you out!
Create an account or sign in to comment