Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.filemaker > #2572 > unrolled thread

Dynamic ( nested) value list

Back to article view | Back to comp.databases.filemaker

Contents

  Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-01 10:14 -0800
    Re: Dynamic ( nested) value list Los_Indios <losindios.m@gmail.com> - 2016-03-01 17:49 -0800
      Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-05 03:13 -0800
    Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-03 18:37 +1300
      Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-03 04:22 -0800
        Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-04 18:22 +1300
          Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-04 10:35 -0800
            Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-05 10:03 +1300
              Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-04 20:10 -0800
                Re: Dynamic ( nested) value list ursus <ursus.kirk@gmail.com> - 2016-03-05 20:46 +0100
                Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-07 13:59 +1300
    Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-08 18:56 +1300
      Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-08 02:54 -0800
        Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-03-09 18:43 +1300
          Re: Dynamic ( nested) value list dempson@actrix.gen.nz (David Empson) - 2016-03-09 21:13 +1300
            Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-10 13:41 -0800
            Re: Dynamic ( nested) value list Thibaud Taudin Chabot <tchabot@hccnet.nl> - 2016-03-11 11:22 +0100
              Re: Dynamic ( nested) value list ursus <ursus.kirk@gmail.com> - 2016-03-11 19:22 +0100
                Re: Dynamic ( nested) value list Thibaud Taudin Chabot <tchabot@hccnet.nl> - 2016-03-12 16:11 +0100
          Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-03-10 13:40 -0800
          Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-04-06 09:41 -0700
            Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-04-07 08:48 +1200
              Re: Dynamic ( nested) value list Mushabab Al-Murayeh <malmurayeh@gmail.com> - 2016-04-08 04:45 -0700
                Re: Dynamic ( nested) value list ursus <ursus.kirk@gmail.com> - 2016-04-08 16:06 +0200
                  Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-04-09 13:20 +1200
                Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-04-09 10:03 +1200
                  Re: Dynamic ( nested) value list dempson@actrix.gen.nz (David Empson) - 2016-04-09 11:20 +1200
                    Re: Dynamic ( nested) value list Helpful Harry <HelpfulHarry@BusyWorking.com> - 2016-04-09 13:29 +1200

Page 1 of 2  [1] 2  Next page →

#2572 — Dynamic ( nested) value list

Hi everyone :)

I would appreciate the help!

I want to build a solution for a medical warehouse  and the database will contain thousands of records of different materials (consumables)   :

I start building the solution but I faced a problem with nested value lists:
I will have 5-6 tables in a file to describe these materials:

1. Category (many items)
2. Class (to be nested to Categories) e.g. many classes belong to one category.
3. Type
4. Size 
5....

Every table of the above belongs to the table above 

I want to have a table where once I choose a category only the related classes pop up in the class field and the same with once I choose a class the related types popup in the type field etc.


Thank you in advance.

Please consider attaching a file as a demonstration to your kind explanation and support.

Thank you in advance.


Mushabab Al-Murayeh, MD

[toc] | [next] | [standalone]

#2573

Τη Τρίτη, 1 Μαρτίου 2016 - 8:14:49 μ.μ. UTC+2, ο χρήστης Mushabab Al-Murayeh έγραψε:
> Hi everyone :)
> 
> I would appreciate the help!
> 
> I want to build a solution for a medical warehouse  and the database will contain thousands of records of different materials (consumables)   :
> 
> I start building the solution but I faced a problem with nested value lists:
> I will have 5-6 tables in a file to describe these materials:
> 
> 1. Category (many items)
> 2. Class (to be nested to Categories) e.g. many classes belong to one category.
> 3. Type
> 4. Size 
> 5....
> 
> Every table of the above belongs to the table above 
> 
> I want to have a table where once I choose a category only the related classes pop up in the class field and the same with once I choose a class the related types popup in the type field etc.
> 
> 
> Thank you in advance.
> 
> Please consider attaching a file as a demonstration to your kind explanation and support.
> 
> Thank you in advance.
> 
> 
> Mushabab Al-Murayeh, MD

Dear friend
your problem is out of my abilities but I recommend you to subscribe and ask at: fmpexperts@lists.ironclad.net.au

Regards
Manos

[toc] | [prev] | [next] | [standalone]

#2580

On Wednesday, March 2, 2016 at 4:49:26 AM UTC+3, Los_Indios wrote:
> Τη Τρίτη, 1 Μαρτίου 2016 - 8:14:49 μ.μ. UTC+2, ο χρήστης Mushabab Al-Murayeh έγραψε:
> > Hi everyone :)
> > 
> > I would appreciate the help!
> > 
> > I want to build a solution for a medical warehouse  and the database will contain thousands of records of different materials (consumables)   :
> > 
> > I start building the solution but I faced a problem with nested value lists:
> > I will have 5-6 tables in a file to describe these materials:
> > 
> > 1. Category (many items)
> > 2. Class (to be nested to Categories) e.g. many classes belong to one category.
> > 3. Type
> > 4. Size 
> > 5....
> > 
> > Every table of the above belongs to the table above 
> > 
> > I want to have a table where once I choose a category only the related classes pop up in the class field and the same with once I choose a class the related types popup in the type field etc.
> > 
> > 
> > Thank you in advance.
> > 
> > Please consider attaching a file as a demonstration to your kind explanation and support.
> > 
> > Thank you in advance.
> > 
> > 
> > Mushabab Al-Murayeh, MD
> 
> Dear friend
> your problem is out of my abilities but I recommend you to subscribe and ask at: fmpexperts@lists.ironclad.net.au
> 
> Regards
> Manos

Thank you for the reply and advise . Unfourtunatly not helpful for me ! :)

[toc] | [prev] | [next] | [standalone]

#2574

In article <dff63d83-8e99-46ba-9193-ccb07a66aecd@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
> 
> Hi everyone :)
> 
> I would appreciate the help!
> 
> I want to build a solution for a medical warehouse  and the database will
> contain thousands of records of different materials (consumables)   :
> 
> I start building the solution but I faced a problem with nested value lists:
> I will have 5-6 tables in a file to describe these materials:
> 
> 1. Category (many items)
> 2. Class (to be nested to Categories) e.g. many classes belong to one
> category.
> 3. Type
> 4. Size 
> 5....
> 
> Every table of the above belongs to the table above 
> 
> I want to have a table where once I choose a category only the related
> classes pop up in the class field and the same with once I choose a class the
> related types popup in the type field etc.
> 
> 
> Thank you in advance.
> 
> Please consider attaching a file as a demonstration to your kind explanation
> and support.
> 
> Thank you in advance.
> 
> 
> Mushabab Al-Murayeh, MD

If I'm reading that correctly, you've got six separate *Tables* to
describe the various materials. You'd be better off with only one
"Materials" Table that contains the data for all of those materials. It
would certainly make the pop-up menu system easier than trying to drill
down through to a sub-sub-sub-sub-sub-sub-Table to get the appropriate
value list data.

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2575

> 
> If I'm reading that correctly, you've got six separate *Tables* to
> describe the various materials. You'd be better off with only one
> "Materials" Table that contains the data for all of those materials. It
> would certainly make the pop-up menu system easier than trying to drill
> down through to a sub-sub-sub-sub-sub-sub-Table to get the appropriate
> value list data.
> 
> Helpful Harry  :o)

Thank you for the reply !

Would you please expand on your idea ?

The table you proposed may become very large !

[toc] | [prev] | [next] | [standalone]

#2576

In article <12c2e85c-70e6-4492-821f-a9bfaa946d6d@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:

> > 
> > If I'm reading that correctly, you've got six separate *Tables* to
> > describe the various materials. You'd be better off with only one
> > "Materials" Table that contains the data for all of those materials. It
> > would certainly make the pop-up menu system easier than trying to drill
> > down through to a sub-sub-sub-sub-sub-sub-Table to get the appropriate
> > value list data.
> > 
> > Helpful Harry  :o)
> 
> Thank you for the reply !
> 
> Would you please expand on your idea ?
> 
> The table you proposed may become very large !

Usually for this type of system you would only need two Tables - one
Table that holds records for all the possible combinations (Stock) and
another Table for the user-entered records (Purchases).

For example, you might have a GroceriesStock Table that has records for:

   Category   Class      Size     Colour
   -------------------------------------
   Fruit      Apple      Large    Red
   Fruit      Apple      Small    Green
   Fruit      Apple      Small    Red
   Fruit      Banana     Medium   Yellow
   Fruit      Banana     Small    Green
   Fruit      Lemon      Small    Yellow
   Veg        Carrot     Small    Orange
   Veg        Lettuce    Medium   Green
   Veg        Lettuce    Large    Green
   Confect.   Choc Bar   Small    Milk
etc.

You would then have another Table which is used to create
ShoppingListPurchases. In this Table, you would have a Category Field
that shows all the possible Categories (Fruit, Veg, Confect., etc.). If
the user chooses "Fruit" from the Category Field, the Class Field's
pop-up menu will show just Apple, Banana, and Lemon. If the user then
chooses "Apple" from this pop-up menu, then the Size Field's pop-up
menu would show only Large and Small. If the user then chooses "Small"
from that pop-up menu, then the Color Field's pop-up menu will show
Green and Red.

If you have separate tables for the four Fields / columns above, then
it becomes very messy (as well as taking up a lot more storage space
and unnecessarily duplicated data) to try and create those Value Lists
for the pop-up menus.

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2577

> You would then have another Table which is used to create
> ShoppingListPurchases. In this Table, you would have a Category Field
> that shows all the possible Categories (Fruit, Veg, Confect., etc.). If
> the user chooses "Fruit" from the Category Field, the Class Field's
> pop-up menu will show just Apple, Banana, and Lemon. If the user then
> chooses "Apple" from this pop-up menu, then the Size Field's pop-up
> menu would show only Large and Small. If the user then chooses "Small"
> from that pop-up menu, then the Color Field's pop-up menu will show
> Green and Red.
> 
> If you have separate tables for the four Fields / columns above, then
> it becomes very messy (as well as taking up a lot more storage space
> and unnecessarily duplicated data) to try and create those Value Lists
> for the pop-up menus.
> 
> Helpful Harry  :o)


Thank you . Let say I will have 
Category (15 )  Class  (for every category 3-6 )   Size  ( for every class 5-10 )    Colour ( for every size 3-7 )

Then how many combination I will have to construct this single table . Beside If I want to add more categories in the future then I have to update all classes, sizes and color !!!!

This why I want to have a table for each ( Category   Class      Size     Color ) to update them separately .

Thank you . Patiently waiting for any response 

[toc] | [prev] | [next] | [standalone]

#2578

In article <147fae8c-b051-4c51-861a-d29a70b077f9@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
> > 
> > You would then have another Table which is used to create
> > ShoppingListPurchases. In this Table, you would have a Category Field
> > that shows all the possible Categories (Fruit, Veg, Confect., etc.). If
> > the user chooses "Fruit" from the Category Field, the Class Field's
> > pop-up menu will show just Apple, Banana, and Lemon. If the user then
> > chooses "Apple" from this pop-up menu, then the Size Field's pop-up
> > menu would show only Large and Small. If the user then chooses "Small"
> > from that pop-up menu, then the Color Field's pop-up menu will show
> > Green and Red.
> > 
> > If you have separate tables for the four Fields / columns above, then
> > it becomes very messy (as well as taking up a lot more storage space
> > and unnecessarily duplicated data) to try and create those Value Lists
> > for the pop-up menus.
> > 
> > Helpful Harry  :o)
> 
> Thank you . Let say I will have 
> Category (15 )  Class  (for every category 3-6 )   Size  ( for every class
> 5-10 )    Colour ( for every size 3-7 )
> 
> Then how many combination I will have to construct this single table . Beside
> If I want to add more categories in the future then I have to update all
> classes, sizes and color !!!!
> 
> This why I want to have a table for each ( Category   Class      Size    
> Color ) to update them separately .
> 
> Thank you . Patiently waiting for any response 

Since the number of Class, Size, etc. varies, there's no way I can
calculate how many records are needed. At worst you need 15 Category x
6 Class x 10 Size x 7 Size ... 6300 records.

You can't ever update them separately since they all need to be linked
upwards and downwards through the separate tables - every time you add
a new "Class" record, you will have to link / add Category records for
the new Class, link / add Size records for the new Class, link / add
Colour records for the new Class.

If you keep them in separate Tables, then to achieve the dynamic pop-up
menus will mean creating new fields which just copy the related data
from the sub-Tables to the parent or child records anyway (every Size
records has to know every Class record that uses it, or every Colour
record it uses), which means the overall filesize will balloon and
likely be bigger than having them in one Table.

Helpful Harry   :o)

[toc] | [prev] | [next] | [standalone]

#2579

> 
> Since the number of Class, Size, etc. varies, there's no way I can
> calculate how many records are needed. At worst you need 15 Category x
> 6 Class x 10 Size x 7 Size ... 6300 records.
> 
> You can't ever update them separately since they all need to be linked
> upwards and downwards through the separate tables - every time you add
> a new "Class" record, you will have to link / add Category records for
> the new Class, link / add Size records for the new Class, link / add
> Colour records for the new Class.
> 
> If you keep them in separate Tables, then to achieve the dynamic pop-up
> menus will mean creating new fields which just copy the related data
> from the sub-Tables to the parent or child records anyway (every Size
> records has to know every Class record that uses it, or every Colour
> record it uses), which means the overall filesize will balloon and
> likely be bigger than having them in one Table.
> 
> Helpful Harry   :o)


Great ! now you know my problem :)

Would you please provide a demo example ? and explain briefly .Thank you

[toc] | [prev] | [next] | [standalone]

#2581

Op 5-3-2016 om 05:10 schreef Mushabab Al-Murayeh:
>
>>
>> Since the number of Class, Size, etc. varies, there's no way I can
>> calculate how many records are needed. At worst you need 15 Category x
>> 6 Class x 10 Size x 7 Size ... 6300 records.
>>
>> You can't ever update them separately since they all need to be linked
>> upwards and downwards through the separate tables - every time you add
>> a new "Class" record, you will have to link / add Category records for
>> the new Class, link / add Size records for the new Class, link / add
>> Colour records for the new Class.
>>
>> If you keep them in separate Tables, then to achieve the dynamic pop-up
>> menus will mean creating new fields which just copy the related data
>> from the sub-Tables to the parent or child records anyway (every Size
>> records has to know every Class record that uses it, or every Colour
>> record it uses), which means the overall filesize will balloon and
>> likely be bigger than having them in one Table.
>>
>> Helpful Harry   :o)
>
>
> Great ! now you know my problem :)
>
> Would you please provide a demo example ? and explain briefly .Thank you
>
  perhaps you can look into the followwing hierarchy solution (which has 
en example download)

http://honza.24usoftware.com/infinite-hierarchy

-- 
Keep well, Ursus

[toc] | [prev] | [next] | [standalone]

#2585

In article <911b3405-279b-4410-a5b5-5a7e38c173c0@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
> > 
> > Since the number of Class, Size, etc. varies, there's no way I can
> > calculate how many records are needed. At worst you need 15 Category x
> > 6 Class x 10 Size x 7 Size ... 6300 records.
> > 
> > You can't ever update them separately since they all need to be linked
> > upwards and downwards through the separate tables - every time you add
> > a new "Class" record, you will have to link / add Category records for
> > the new Class, link / add Size records for the new Class, link / add
> > Colour records for the new Class.
> > 
> > If you keep them in separate Tables, then to achieve the dynamic pop-up
> > menus will mean creating new fields which just copy the related data
> > from the sub-Tables to the parent or child records anyway (every Size
> > records has to know every Class record that uses it, or every Colour
> > record it uses), which means the overall filesize will balloon and
> > likely be bigger than having them in one Table.
> > 
> > Helpful Harry   :o)
> 
> Great ! now you know my problem :)
> 
> Would you please provide a demo example ? and explain briefly .Thank you

It'll take a while to work this out and type it up into a message as a
coherent explanation.

Even if you keep the multiple nested Tables approach, it's probably
better to decrease the number of Tables, even if it means increasing
the number of options in some of them (e.g. instead of separate Size
and Colour Tables, it might be easier to have a combined Size-Colour
Table).

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2586

In article <dff63d83-8e99-46ba-9193-ccb07a66aecd@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:

> Hi everyone :)
> 
> I would appreciate the help!
> 
> I want to build a solution for a medical warehouse  and the database will
> contain thousands of records of different materials (consumables)   :
> 
> I start building the solution but I faced a problem with nested value lists:
> I will have 5-6 tables in a file to describe these materials:
> 
> 1. Category (many items)
> 2. Class (to be nested to Categories) e.g. many classes belong to one
> category.
> 3. Type
> 4. Size 
> 5....
> 
> Every table of the above belongs to the table above 
> 
> I want to have a table where once I choose a category only the related
> classes pop up in the class field and the same with once I choose a class the
> related types popup in the type field etc.
> 
> 
> Thank you in advance.
> 
> Please consider attaching a file as a demonstration to your kind explanation
> and support.
> 
> Thank you in advance.
> 
> 
> Mushabab Al-Murayeh, MD

Okay, this didn't work out as bad as I thought it was going to have to
be. I figured out a way for using five nested tables that is fairly
compact and easy (and simple to add more sub-tables to) ... but
complicated to explain in a text message

It does also make a few assumptions about how your system is designed -
the main one being that the Relationship links to the next sub-Table
records are stored in a normal Text Field, with each separate
Relationship Link on a new line. It also requires the pop-up menus for
the user to display both a ID number and item name.

You didn't say what version of FileMaker Pro you're using, but this
should work in any version from at least FileMaker Pro 4 onwards
(probably any version with Relationship abilities).

Sample files to be tidied up and uploaded ... if I can find somewhere
to upload them!



SETTING-UP

First you've got the five nested data Tables, with each sub-Table
related from the Table above it in a One:Many system. 

    Category
    - Class
    -- Type
    --- Size
    ---- Brand

These need to have at least four Fields: a unique ID Field, the name 
Field, a Field that combines these two, and a Field for links to the
next sub-Table (not needed in the bottom-most Table). They each also
obviously need a Relationship to the next sub-Table. 
e.g

    CategoryTable
       Fields:
          CategoryID                 Text  Auto-enter Serial Number
                                           starting with Cat001
          CategoryName               Text
          c_CategoryID_CategoryName  Calculation (Text Result)
                                     = CategoryID & " - " & CategoryName
          ClassLinks                 Text

       Relationship:
          rel_Classes                ClassLinks = ::ClassID   ClassTable


    ClassTable
       Fields:
          ClassID                    Text  Auto-enter Serial Number
                                           starting with Cls001
          ClassName                  Text
          c_ClassID_ClassName        Calculation (Text Result)
                                     = ClassID & " - " & ClassName
          TypeLinks                  Text
 
       Relationship:
          rel_Types                  TypeLinks = ::TypeID     TypeTable


    TypeTable
       Fields:
          TypeID                     Text  Auto-enter Serial Number
                                           starting with Typ001
          TypeName                   Text
          c_TypeID_TypeName          Calculation (Text Result)
                                     = TypeID & " - " & TypeName
          SizeLinks                  Text
 
       Relationship:
          rel_Sizes                  SizeLinks = ::SizeID     SizeTable


    SizeTable
       Fields:
          SizeID                     Text  Auto-enter Serial Number
                                           starting with Siz001
          SizeName                   Text
          c_SizeID_SizeName          Calculation (Text Result)
                                     = SizeID & " - " & SizeName
          BrandLinks                 Text
 
       Relationship:
          rel_Brands                 BrandLinks = ::BrandID   BrandTable


    BrandTable
       Fields:
          BrandID                    Text  Auto-enter Serial Number
                                           starting with Bnd001
          BrandName                  Text
          c_BrandID_BrandName        Calculation (Text Result)
                                     = BrandID & " - " & BrandName


The main UserTable is the one for the user data entry (the one that
will have the pop-up menus). This needs to have at least 13 Fields,
eight Relationships linking to the five data Tables above (one each for
the top and bottom Tables, and two for the each of the middle Tables),
and five Value Lists (one for each pop-up menu Field).

    UserTable
       Fields:
          UserCategory               Text  
                                     formatted as Pop-up Menu using
                                     vl_UserCategoryList
          UserClass                  Text  
                                     formatted as Pop-up Menu using
                                     vl_UserClassList
          UserType                   Text  
                                     formatted as Pop-up Menu using
                                     vl_UserTypeList
          UserSize                   Text  
                                     formatted as Pop-up Menu using
                                     vl_UserSizeList
          UserBrand                  Text  
                                     formatted as Pop-up Menu using
                                     vl_UserBrandList

          c_UserCategoryID           Calculation (Text Result)
                                     = Left(UserCategory, 6)
          c_UserClassID              Calculation (Text Result)
                                     = Left(UserClass, 6)
          c_UserTypeID               Calculation (Text Result)
                                     = Left(UserType, 6)
          c_UserSizeID               Calculation (Text Result)
                                     = Left(UserSize, 6)

          c_ClassLinksLookup         Calculation (Text Result)
                             = rel_LookupCategory_Classes::ClassLinks
          c_TypeLinksLookup         Calculation (Text Result)
                             = rel_LookupClass_Types::TypeLinks
          c_SizeLinksLookup         Calculation (Text Result)
                             = rel_LookupType_Sizes::SizeLinks
          c_BrandLinksLookup         Calculation (Text Result)
                             = rel_LookupSize_Brands::BrandLinks

       Relationships:
          rel_LookupCategory_Classes  c_UserCategoryID = ::CategoryID  
                                               CategoryTable
          rel_LookupClass_Types       c_UserClassID = ::ClassID  
                                               ClassTable
          rel_LookupType_Sizes        c_UserTypeID = ::TypeID  
                                               TypeTable
          rel_LookupSize_Brands       c_UserSizeID = ::SizeID    
                                               SizeTable

          rel_Class_Popup             c_ClassLinksLookup=::ClassID  
                                               ClassTable
          rel_Type_Popup              c_TypeLinksLookup=::TypeID  
                                               TypeTable
          rel_Size_Popup              c_SizeLinksLookup=::SizeID   
                                               SizeTable
          rel_Brand_Popup             c_BrandLinksLookup=::BrandID   
                                               BrandTable

       Value Lists:
          vl_UserCategoryList    From Field   c_CategoryID_CategoryName
                                               CategoryTable
          vl_UserClassList       From Field   c_ClassID_ClassName
                                 only related values: rel_Class_Popup
          vl_UserTypeList        From Field   c_TypeID_TypeName
                                 only related values: rel_Type_Popup
          vl_UserSizeList        From Field   c_SizeID_SizeName
                                 only related values: rel_Size_Popup
          vl_UserBrandList       From Field   c_BrandID_BrandName
                                 only related values: rel_Brand_Popup


That's the set-up done ... now on how it works when entering data in
the UserTable using the five pop-up menu Fields.



HOW IT WORKS

Basically it copies the Relationship links from each pop-up menu's
chosen parent Table record so that data can be used in a Relationship
link from the UserTable to the next child Table.

The UserCategory Field uses the vl_UserCategoryList Value List to
retrieve *ALL* the category records from the CategoryTable. These are
displayed as both the ID number and the name.
e.g.
        Cat001 - Fruit
        Cat002 - Vegetables
        Cat003 - Confectionery
      etc.

You need ID so that the UserTable can work out which record to retrieve
the appropriate sub-Table links from. You could potentially do this in
other ways, but it can get messy if they aren't uniquely identifiable.

When the user picks one of these Category menu options, the
c_UserCategoryID Calculation Field extracts the first six characters
(i.e. the CategoryID) which can then be used via the
rel_LookupCategory_Classes Relationship to retrieve the appropriate
Class Links from the CategoryTable's ClassLinks Field. These related
link IDs are stored in the c_ClassLinksLookup Calcluation Field.The
c_ClassLinksLookup Calculation Field can then be used via the
rel_Class_Popup Relationship to allow the vl_UserClassList Value List
to retrieve only the appropriate related possibilities for the
UserClass pop-up menu Field from the ClassTable.
e.g.
    If the user chooses UserCategory option "Cat002 - Vegetables"
    then the UserClass pop-up menu would display

        Cls001 - Carrot
        Cls002 - Cauliflower
        Cls003 - Cabbage
        Cls004 - Lettuce
      etc.

When the user picks one of these Class menu options, the process
repeats with the "Type" set of Fields, Relationships, and Value List to
retrieve the appropriate related possibilities for the UserType pop-up
menu Field from the TypeTable. 

And so on, down through to the fifth pop-up menu.

If you need to add another sub-Table {NEWITEM}Table to the bottom of
the nested sub-Tables, then the {PREVIOUSITEM}Table needs these
additions:

      Fields:
          {NEWITEM}Links     Text
 
       Relationship:
          rel_{NEWITEM}      {NEWITEM}Links = ::{NEWITEM}ID  
                                               {NEWITEM}Table


the {NEWITEM}Table needs these:

       Fields:
          {NEWITEM}ID                   Text  Auto-enter Serial Number
                                        starting with {NEWCODE}001
          {NEWITEM}Name                 Text
          c_{NEWITEM}ID_{NEWITEM}Name   Calculation (Text Result)
                                   = {NEWITEM}ID & " - " & {NEWITEM}Name


and finally the UserTable needs these additions:

      Fields:
          User{NEWITEM}            Text  
                                   formatted as Pop-up Menu using
                                   vl_User{NEWITEM}List
  
          c_User{PREVIOUSITEM}ID   Calculation (Text Result)
                                   = Left(User{NEWITEM}, 6)

          c_{NEWITEM}LinksLookup   Calculation (Text Result)
                       = rel_Lookup{PREVIOUSITEM}_NEWITEM::NEWITEMLinks

       Relationships:
          rel_Lookup{PREVIOUSITEM}_{NEWITEM}   
                         c_User{PREVIOUSITEM}ID = ::{PREVIOUSITEM}ID  
                                               {PREVIOUSITEM}Table

          rel_{NEWITEM}_Popup      c_{NEWITEM}LinksLookup=::{NEWITEM}ID 

                                               {NEWITEM}Table

       Value Lists:
          vl_User{NEWITEM}List   From Field  c_{NEWITEM}ID_{NEWITEM}Name
                                             only related values:  
                                             rel_{NEWITEM}_Popup



Hopefully that makes some sort of sense.

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2587

> 
> Sample files to be tidied up and uploaded ... if I can find somewhere
> to upload them!
> 

> 
> Hopefully that makes some sort of sense.
> 
> Helpful Harry  :o)


Thank you so much Helpful Harry! for your Helpful ideas!
I do appreciate the time you took to think about this and typing it down!

I will try to apply it. Awaiting your sample files :)


Mushabab AL-Murayeh, MD

[toc] | [prev] | [next] | [standalone]

#2588

In article <f994f4a8-bd36-4879-8bda-c1a614a5bb8a@googlegroups.com>,
Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
> > 
> > Sample files to be tidied up and uploaded ... if I can find somewhere
> > to upload them!
> > 
><snip> 
> > 
> > Hopefully that makes some sort of sense.
> > 
> > Helpful Harry  :o)
> 
> Thank you so much Helpful Harry! for your Helpful ideas!
> I do appreciate the time you took to think about this and typing it down!
> 
> I will try to apply it. Awaiting your sample files :)
> 
> Mushabab AL-Murayeh, MD

I've uploaded the sample files as a Zip archive (only 20K) to:
http://filesave.me/file/125614/Nested-Menus-Sample-Files-zip.html

The files are automatically delete 30 days after the last download, so
that should be more than enough time.

It's a Zip archive containing six database files:

    UserTable.fp5
    CategoryTable.fp5
    ClassTable.fp5
    TypeTable.fp5
    SizeTable.fp5
    BrandTable.fp5

Because I'm still using an old version of FileMaker Pro, these are
FileMaker Pro 5 documents where each Table is a separate document. You
should be able to convert them to a newer version (I'm not sure how on
Windows, but on a Mac just drag *all* the documents at the same time
onto the FileMaker Pro application / Dock icon).

I haven't bothered entering a huge amount of sample data. You can add
more or delete the existing records in the Tables to add your own data
to try the menus with.

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2589

Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:

> In article <f994f4a8-bd36-4879-8bda-c1a614a5bb8a@googlegroups.com>,
> Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
> > > 
> > > Sample files to be tidied up and uploaded ... if I can find somewhere
> > > to upload them!
> > > 
> ><snip> 
> > > 
> > > Hopefully that makes some sort of sense.
> > > 
> > > Helpful Harry  :o)
> > 
> > Thank you so much Helpful Harry! for your Helpful ideas!
> > I do appreciate the time you took to think about this and typing it down!
> > 
> > I will try to apply it. Awaiting your sample files :)
> > 
> > Mushabab AL-Murayeh, MD
> 
> I've uploaded the sample files as a Zip archive (only 20K) to:
> http://filesave.me/file/125614/Nested-Menus-Sample-Files-zip.html
> 
> The files are automatically delete 30 days after the last download, so
> that should be more than enough time.
> 
> It's a Zip archive containing six database files:
> 
>     UserTable.fp5
>     CategoryTable.fp5
>     ClassTable.fp5
>     TypeTable.fp5
>     SizeTable.fp5
>     BrandTable.fp5
> 
> Because I'm still using an old version of FileMaker Pro, these are
> FileMaker Pro 5 documents where each Table is a separate document. You
> should be able to convert them to a newer version (I'm not sure how on
> Windows, but on a Mac just drag *all* the documents at the same time
> onto the FileMaker Pro application / Dock icon).

Same on Windows, but on either platform note that you won't be able to
open those files in FileMaker Pro 12 or later, because recent versions
don't support importing databases in the file format of FileMaker Pro 6
and earlier.

The workaround is to download a trial edition of FileMaker Pro 11, use
it to convert the older files to .fp7 format, then import those in the
later version.

http://help.filemaker.com/app/answers/detail/a_id/10571/~/converting-older-filemaker-pro-files-to-the-.fmp12-file-format

> I haven't bothered entering a huge amount of sample data. You can add
> more or delete the existing records in the Tables to add your own data
> to try the menus with.


-- 
David Empson
dempson@actrix.gen.nz

[toc] | [prev] | [next] | [standalone]

#2591

Thank you David that what I did :)

[toc] | [prev] | [next] | [standalone]

#2592

Op 9-3-2016 om 9:13 schreef David Empson:
> Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:
>
>> In article <f994f4a8-bd36-4879-8bda-c1a614a5bb8a@googlegroups.com>,
>> Mushabab Al-Murayeh <malmurayeh@gmail.com> wrote:
>>>>
>>>> Sample files to be tidied up and uploaded ... if I can find somewhere
>>>> to upload them!
>>>>
>>> <snip>
>>>>
>>>> Hopefully that makes some sort of sense.
>>>>
>>>> Helpful Harry  :o)
>>>
>>> Thank you so much Helpful Harry! for your Helpful ideas!
>>> I do appreciate the time you took to think about this and typing it down!
>>>
>>> I will try to apply it. Awaiting your sample files :)
>>>
>>> Mushabab AL-Murayeh, MD
>>
>> I've uploaded the sample files as a Zip archive (only 20K) to:
>> http://filesave.me/file/125614/Nested-Menus-Sample-Files-zip.html
>>
>> The files are automatically delete 30 days after the last download, so
>> that should be more than enough time.
>>
>> It's a Zip archive containing six database files:
>>
>>      UserTable.fp5
>>      CategoryTable.fp5
>>      ClassTable.fp5
>>      TypeTable.fp5
>>      SizeTable.fp5
>>      BrandTable.fp5
>>
>> Because I'm still using an old version of FileMaker Pro, these are
>> FileMaker Pro 5 documents where each Table is a separate document. You
>> should be able to convert them to a newer version (I'm not sure how on
>> Windows, but on a Mac just drag *all* the documents at the same time
>> onto the FileMaker Pro application / Dock icon).
>
> Same on Windows, but on either platform note that you won't be able to
> open those files in FileMaker Pro 12 or later, because recent versions
> don't support importing databases in the file format of FileMaker Pro 6
> and earlier.
>
> The workaround is to download a trial edition of FileMaker Pro 11, use
> it to convert the older files to .fp7 format, then import those in the
> later version.
>
> http://help.filemaker.com/app/answers/detail/a_id/10571/~/converting-older-filemaker-pro-files-to-the-.fmp12-file-format
>
>> I haven't bothered entering a huge amount of sample data. You can add
>> more or delete the existing records in the Tables to add your own data
>> to try the menus with.
>
>
is there somebody who could convert those .fp5 files through the 
mentioned .fp7 files into .fp12 files and make those .fp12 files 
available for download?

[toc] | [prev] | [next] | [standalone]

#2593

>>
>>
> is there somebody who could convert those .fp5 files through the
> mentioned .fp7 files into .fp12 files and make those .fp12 files
> available for download?

i've done that for you. completely untested. download from:
https://dl.dropboxusercontent.com/u/30381737/Nested%20menu%20sample.zip

-- 
Keep well, Ursus

[toc] | [prev] | [next] | [standalone]

#2594

Op 11-3-2016 om 19:22 schreef ursus:
>
>>>
>>>
>> is there somebody who could convert those .fp5 files through the
>> mentioned .fp7 files into .fp12 files and make those .fp12 files
>> available for download?
>
> i've done that for you. completely untested. download from:
> https://dl.dropboxusercontent.com/u/30381737/Nested%20menu%20sample.zip
>
thanks

[toc] | [prev] | [next] | [standalone]

#2590

Thank you Helpful Harry 

I have FM 14 and will try to convert the files to tables in one file!

MA

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.databases.filemaker

csiph-web