Yes. This why f.e. when clients want to add a lot of product specification fields to the Item card I create a table called Item Configuration, linked to the Item by primary key.
1:
Miklos' appproach. This is the most flexible one, although you really want to prevent one-to-one relationships in a relational database, they are a pain to maintain.
2:
disable fields that you're not using. This is a very dangerous approach, because you'd be in trouble if your customer ever decides to start using that field.
Comments
For any queries you can also visit my blog site: http://msnavarena.blogspot.com/
1:
Miklos' appproach. This is the most flexible one, although you really want to prevent one-to-one relationships in a relational database, they are a pain to maintain.
2:
disable fields that you're not using. This is a very dangerous approach, because you'd be in trouble if your customer ever decides to start using that field.
RIS Plus, LLC