Y
I'm working on a project that requires recipe data to be stored in SQL server. I implemented as system where each recipe type has a template. The template lists a field number in one column and a tag name in the adjacent column.
Recipes are stored in a separate table. This table has numbered field names. The field names coorespond to the field numbers in the 1st column of the template table.
This system works pretty well but it has 2 major drawbacks:
1) The data is only logically linked to it's field name.
2) It is difficult to maintain. The user frequently adds fields without updating the template and/or recipe table.
I was wondering if anyone has an alternate design that is more robust than the one described above.
Thanks,
(8{)} ( .)
[email protected]
Recipes are stored in a separate table. This table has numbered field names. The field names coorespond to the field numbers in the 1st column of the template table.
This system works pretty well but it has 2 major drawbacks:
1) The data is only logically linked to it's field name.
2) It is difficult to maintain. The user frequently adds fields without updating the template and/or recipe table.
I was wondering if anyone has an alternate design that is more robust than the one described above.
Thanks,
(8{)} ( .)
[email protected]
