dynamic data entry system

[David Mueller]

I've been tasked to create a data entry system whose data elements,
validation tables, and constraints vary from case to case. There may be a
single term for such a project. I need it to function similar to the way a
wizard works.

In other words, I'm trying to deliver an MS Access database that contains
tables, forms, and code capable of creating "on the fly" the case-specific
tables, forms and code required to create the actual data entry system.

The data elements I have been given are not normalized. For example, there
are fields called SALARY_1, SALARY_2 ... SALARY_10. Some cases will require
3 iterations of SALARY, other cases will use more or less. Further, the
system needs to spit out the collected data in this non-normalized form.

So far, I have a DATA_ELEMENT table (180+ elements), which contains the
ELEMENT_ID, and other information required to place that element on a field
in the right position, name it, fill with default values, a rowsource if
listbox or combobox, etc...

The complexity is starting to crush my chest. Does anyone know if I'm
heading in the right direction? Should I normalize the data elements I have
been given, only to "un-normalize" them on the output? Will building a
dynamic, good looking form be impossible on this scale?

Thanks

 

[KARL DEWEY]

Normalize the data and use a crosstab query to display it like they want it.

Maybe you need a connecting table that is linked one-to-many from projects
and linked one-to-many from constraints.

 

[peregenem]

I've been tasked to create a data entry system whose data elements,
validation tables, and constraints vary from case to case. There may be a
single term for such a project.

If I have understood correctly, the name of this design flaw is EAV
("Entity-Attribute-Value").