CD Collection Model - Erwin

First version:
RED Tables are not valid for the model.

Working with ERwin

The doubt about type identifying or non-identifying:

identifying means migrate the pk to become a new pk for the other table as well.

Non-identifying means migrate the pk to become foreign key for the other table.

create two tables:

to break up a N:N relationship, use IDENTIFYING type.

I still don't know how to use this symbol, knowing that it doesn't help much.

Working with Power Designer

When I stay some time away from Power designer, I forget the basics stuffs to do. So to remember, I put this post.

The first thing we should do is to create the tables as usual:

then you create the dependency between them:

now you must create an index UNIQUE for the PK, double click on the table:

last step is to double click on the index you have just created to reference to the PK on the columns definition droplist box:

Voilà, after creating the index and point to the pk for the city table, now check

if you have any errors or warnings, click F4 for "check model". Good job.

Data Modeling Studies: Band and Members

CA ERwin

Sybase PowerDesigner

MS Access 2000