Page 1 of 2 12 LastLast
Results 1 to 15 of 16

Thread: Form tabs?

  1. #1
    Join Date
    Aug 2006
    Posts
    559

    Unanswered: Form tabs?

    So I'm in the market to try something new in this new database I'm working on.

    You know how MS Excel has different sheets, like tabs at the bottom of the file? Is this possible to do in MS Access? I'm asking because I have different items (Personal Information, Travel, Destination, Visa, etc) that I wanted to display as a SINGLE record on an individual, however, be able to allow the user to click on the individual tabs to enter in the information.

    Then that will bring me to the next question...

    What if I have more than one entry? Like if the person has 2 or more points of "Travel" or "Destination" and I need it to be added into the same individual's record. Can this happen? ***Stab in the dark, but I think that'd be a subform??**

    Anyone do anything like this before? Help me out? Is it possible? Impossible? What?

    Thanks all!

  2. #2
    Join Date
    Apr 2004
    Location
    metro Detroit
    Posts
    634
    Play with the tab control on a form. Put a subform on one or more of the pages on the tab control.

  3. #3
    Join Date
    Aug 2006
    Posts
    559
    Ok Rogue, I'll look into that.

    Now if I use this method, do I need to create a new table to be displayed on each of those particular tabs? For instance...

    Tab 1: All personal data
    Tab 2: All vehicular data
    Tab 3: All Travel data
    etc, etc?

    For instance, what I found at this link

  4. #4
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    No.

    You can put anything on any tab page.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  5. #5
    Join Date
    Aug 2006
    Posts
    559
    Thanks for the reply Trekk. Someone suggested it'd be easier to use like sub-forms but after taking a look at them and what they are, I think that it'd be too difficult to do what I want and have the user be able to make sense out of it.

  6. #6
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    It always comes down to your needs. You need a subform on a tab control when you want to show the many side of a relationship. For example, if you had this:

    CUSTOMER 1-------M ORDERS

    You could have a Customer form, with a tab control on it that divides up the different areas / categories for the customer and another tab with a subform that shows a summary of all the customer's orders.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  7. #7
    Join Date
    Aug 2006
    Posts
    559
    So then my...

    Individual = 1 <---> Travel Destination = many , etc, etc, will be better with the Tab Control versus the Subform on the main form? Yes?

  8. #8
    Join Date
    Apr 2004
    Location
    metro Detroit
    Posts
    634
    Create a form based on your 'Individual' data. Create a form based on your 'Travel Destination' data.

    Put a tab control on your 'Individual' form. On one of the pages of the tab control, add your 'Destination' form (as a sub form). You can break up your 'Individual' data on other pages of the tab control or put other sub forms (for any other 1 - many relationships) on the the pages.

  9. #9
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Quote Originally Posted by Grafixx01
    So then my...

    Individual = 1 <---> Travel Destination = many , etc, etc, will be better with the Tab Control versus the Subform on the main form? Yes?
    No. If you have many Travel Destination records for the one individual, then the ONLY efficient way to show both on the same screen is to have the individual on a mainform and the travel destinations on a subform.

    Having a Tab Control just makes it so you don't need to scroll around.

    Think of a Tab Control as a way to have many screens / pages in the same form area. It doesn't effect the form itself.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  10. #10
    Join Date
    Aug 2006
    Posts
    559
    Quote Originally Posted by StarTrekker
    No. If you have many Travel Destination records for the one individual, then the ONLY efficient way to show both on the same screen is to have the individual on a mainform and the travel destinations on a subform.

    Having a Tab Control just makes it so you don't need to scroll around.

    Think of a Tab Control as a way to have many screens / pages in the same form area. It doesn't effect the form itself.
    Dang, that stinks! I was hoping to make it have an appearance like a manilla-folder file system just all the tabs would be for a single person, with the tabs meaning different things.

    I'm saying cause I have "tblIndividual" which is the main table. Then the tables that relate to that Individual which can have multiple instances are:

    Passport + Passport Travel (could have multiple passports and want to record the countries and dates of travel in / out of those countries).
    Purpose of Travel to Mexico (can travel to Mexico multiple occasions and different destinations)
    U.S. Travel Destination (Can travel inside the states on multiple occasions to different destinations)
    Visa (a person can have multiple Visas)
    State Identification (could be DLs, Permits, ID Cards, also has the class)
    Point-of-Entry (the crossing of the border that they are at or checkpoint)
    Travel Method (could be car, truck, bike, foot, etc).

    So as you can see, you could figure why I would rather see it be a tabbed-main form for data entry because I figured that the single-form would be way too long and complex to understand.

    Agree? Disagree?

  11. #11
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    So you want to have a mainform where each person as a different tab in a tab control? That would be problematic at best... especially if you have 10000 individuals.

    A single form can handle all that, but you would have to have one subform for each of those tables related to the individual (every table which has IndividualID as a foreign key). Each subform can be on a different tab control page though, so one screen with all it's tab control pages refer to one individual.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  12. #12
    Join Date
    Aug 2006
    Posts
    559
    Quote Originally Posted by StarTrekker
    So you want to have a mainform where each person as a different tab in a tab control? That would be problematic at best... especially if you have 10000 individuals.

    A single form can handle all that, but you would have to have one subform for each of those tables related to the individual (every table which has IndividualID as a foreign key). Each subform can be on a different tab control page though, so one screen with all it's tab control pages refer to one individual.
    Well, what I was thinking was having the Main form as the First tab which would just hold the Individual's personal information.
    Then...
    Tab 2, with just the full-name of the SAME individual on it, could display like the State Identification Information.
    Tab 3, with just the full-name of the SAME individual on it, could display the Passport Information.
    Tab 4, with just the full-name of the SAME individual on it, could display the Travel Information.
    Tab 5, with just the full-name of the SAME individual on it, could display the Point-of-Entry Information.
    With other tabs like the above. ALL of these tabs would be on a SINGLE individual, much like how those "index tabs" you can buy for binders work or an excel spreadsheet looks.

    So when the user opens the main form from the Main Menu form, they will see ALL of the individual's personal information on different tabs rather than an elongated form. I just figure that would be way too complex for these users here to understand unless I document the main form extremely well on what all of the different sections are.

  13. #13
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Sounds like a plan

    Trust me, users adapt to having different details of an element on different tabs very quickly.

    I suggest you have the full name of the individual above and outside of the tab control so that you don't have to have multiple copies of the same field.

    [form]
    ========================================
    Common Individual Fields: (ID, firstname, surname)
    ____ ____ ____ ___
    /tab1\/tab2\/tab3\/etc\

    ========================================
    [/form]
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  14. #14
    Join Date
    Aug 2006
    Posts
    559
    Quote Originally Posted by StarTrekker
    Sounds like a plan

    Trust me, users adapt to having different details of an element on different tabs very quickly.

    I suggest you have the full name of the individual above and outside of the tab control so that you don't have to have multiple copies of the same field.

    [form]
    ========================================
    Common Individual Fields: (ID, firstname, surname)
    ____ ____ ____ ___
    /tab1\/tab2\/tab3\/etc\

    ========================================
    [/form]

    Yeah, that's the way I was thinking of doing it otherwise. Just putting one name on the form like a Header / Footer, then all the tabs in it so they know it only pertains to that one individual.

    **You must remember that I work in a bureaucracy so people want it as stupid-easy , well they need it that way too, as possible otherwise after I do it, I'll just have to redesign the entire thing. That's not something that I want to do!

  15. #15
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Ah yes, making applications AIP (almost idiot proof) is often a difficult task! ^.^
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •