Re: Data Mapping in Designer/ 2000

Jim and Jeff,

We too have wrestled with the need for one common model to interrelate our multiple physical models. We explored the use of the table-entity mapping and found the limitations that Jeff identified. What we are considering as a possible solution is a variation on Jeff's suggestion.

> An alternate solution is to create an ER model, and possibly physical models,
> but instead of using the built-in associations, create your own "association"
> tables using the meta-model view of entity, attributes, columns, tables, etc.

We are thinking about implementing a three tier model: Conceptual, logical, and physical. The latter two would function largely as they do today. The conceptual model would be an ER model which is mapped to the logical ER models. We are aware that this mapping has to be very accomodating because an attribute in a logical model (say manager's name) may reflect a relationship in the conceptual model. It would also be desirable to record encodings and restrictions on these mappings. Are there any comments on this approach? Thanks. Cory Received on Tue Feb 25 1997 - 00:00:00 CET