Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
HOW DO YOU CREATE TABS?
- Thread starter jb001
- Start date
Tabs are simply buttons you create to look like tabs. I know Access allows you to drag and drop a tab interface but who wants to use Access?
If you do a search under google.com, you will find a lot of examples that you can download for free. These are sample templates that you can take apart to figure out how they work.
A tab though can be a field or button. The field might be a one you cannot enter that carries color into the tab. This works great to help identify if the tab is an up tab or a down tab. Check out They also have a build a tab interface example there to.
One thing I want point out if you are a newbee is that the tab interface needs to be consistant with all pages of your solution. Build what you want it to look like for every screen on one layout. Were not talking about any fields, just the layout. Then duplicated the layout for safe keeping. You can always come back to that page to Copy your layout for pasting on to a new layout.
I remember the first solution I built. It had tabs and changes to the interface. Multiple layouts. Push a button or tab here and it took you to that layout, and being a newbee, I did understand that I had created a tabbed and button interface that required the use of a dozen different data bases to execute everything I wanted to do. I had built fields, calculations, it worked great, then some whee in there I hit new file and realized I made a huge mistake. Information I wanted all files to access was in the press file only and not available to all records. A tough learning lesson that began the relational database learning and understanding. Words of wisdom is understand the total scope of how many databases you need, then take the tabbed interface throughout all of the different databases. Then when the user presses a tab, he changes to the correct database. He doesn't really know this because the tab interface looks the same except that may a darker tab marks the new location and the screen refreshes with the desired information.
Check out the screen shots at for a Filemaker solution with extensive tabbed interface.
I hope this helps you on your way.
Marty
If you do a search under google.com, you will find a lot of examples that you can download for free. These are sample templates that you can take apart to figure out how they work.
A tab though can be a field or button. The field might be a one you cannot enter that carries color into the tab. This works great to help identify if the tab is an up tab or a down tab. Check out They also have a build a tab interface example there to.
One thing I want point out if you are a newbee is that the tab interface needs to be consistant with all pages of your solution. Build what you want it to look like for every screen on one layout. Were not talking about any fields, just the layout. Then duplicated the layout for safe keeping. You can always come back to that page to Copy your layout for pasting on to a new layout.
I remember the first solution I built. It had tabs and changes to the interface. Multiple layouts. Push a button or tab here and it took you to that layout, and being a newbee, I did understand that I had created a tabbed and button interface that required the use of a dozen different data bases to execute everything I wanted to do. I had built fields, calculations, it worked great, then some whee in there I hit new file and realized I made a huge mistake. Information I wanted all files to access was in the press file only and not available to all records. A tough learning lesson that began the relational database learning and understanding. Words of wisdom is understand the total scope of how many databases you need, then take the tabbed interface throughout all of the different databases. Then when the user presses a tab, he changes to the correct database. He doesn't really know this because the tab interface looks the same except that may a darker tab marks the new location and the screen refreshes with the desired information.
Check out the screen shots at for a Filemaker solution with extensive tabbed interface.
I hope this helps you on your way.
Marty
- Status
Similar threads
- Locked
- Question
- Locked
- Question