I want to define a group of normalized tables so that it is straightforward to define new types of detail fields in a data dictionary to accomodate customer requests.

At runtime I will use a crosstab cursor to group detail fields into logical (virtual) records. These virtual records will be used for data entry, in grids, in reports etc. The records will contain all columns defined in the data dictionary.

I am tempted to split the virtual records in two. The first part would be a physical table with the fields common to all users of the application, and the second part would be a cross table with the extra fields defined in the data dictionary. The physical table and the virtual table would have a one to one relationship. The motivation is that is seems like a big waste of resources to always have to create a cross tab table that includes "permament" fields.

I'd welcome your comments and recommendations.

TIA,

Alex