Hi All,
In my scenario
Single products night be thinks like 2-inch wheel or 1 inch wheel in a choice of colours, front axle, back axle etc that can be ordered as distinct products
A kit is distinct product in its own right consisting of a bundled set of other single product components.
Question 1: I would quite like to have single products and kits use the same ProductID index but I think Single products and kits need to be on separate tables in order that the product components included in a kit can be defined. So what I would like to happen is that if I open a kit form on my database in order to define a new kit that it would somehow look at the index for the single product table and take the next assigned ProductID. I am not sure of the best design approach with regards to tables and relationships needed to enable this so suggestions would be welcome.
Question 2: When associating the single product components of a kit with the kit record it will be necessary to select from the entire list or single product components as all single products are potentially valid kit components. If I were to do this using the tbl_single_products as a lookup table it would be a very long lookup list the user would have to scroll through. Are there any functions or techniques that would allow me to dynamically search a lookup list as the user enters text e.g. The user enters "T" the list pointer goes to entries beginning with "T" the user enters "e" the list pointer goes to lookup list entries beginning in "Te" etc.
Question 3: Is there anyway apart from autonumber to create an automatically incrementing index of your choice for use in tables e.g. PROD001, PROD002 etc
Hope that is enough to elicit some feedback,
Many thanks
HowardB
In my scenario
Single products night be thinks like 2-inch wheel or 1 inch wheel in a choice of colours, front axle, back axle etc that can be ordered as distinct products
A kit is distinct product in its own right consisting of a bundled set of other single product components.
Question 1: I would quite like to have single products and kits use the same ProductID index but I think Single products and kits need to be on separate tables in order that the product components included in a kit can be defined. So what I would like to happen is that if I open a kit form on my database in order to define a new kit that it would somehow look at the index for the single product table and take the next assigned ProductID. I am not sure of the best design approach with regards to tables and relationships needed to enable this so suggestions would be welcome.
Question 2: When associating the single product components of a kit with the kit record it will be necessary to select from the entire list or single product components as all single products are potentially valid kit components. If I were to do this using the tbl_single_products as a lookup table it would be a very long lookup list the user would have to scroll through. Are there any functions or techniques that would allow me to dynamically search a lookup list as the user enters text e.g. The user enters "T" the list pointer goes to entries beginning with "T" the user enters "e" the list pointer goes to lookup list entries beginning in "Te" etc.
Question 3: Is there anyway apart from autonumber to create an automatically incrementing index of your choice for use in tables e.g. PROD001, PROD002 etc
Hope that is enough to elicit some feedback,
Many thanks
HowardB