Otis wrote:
You need Foreign key constraints in your tables (from FK side to PK side), and then the relations are added automatically.
However, if the FK constraints aren't defined correctly, they're not picked up. Please check the Application output window after the refresh to see if it ignored FK constraints. Also, if you defined hte FK constraint on the PK table, it won't be picked up as that's backwards, you've to define them on the FK table. (e.g. Customer & Order, the FK has to be defined on Order, pointing to Customer)
Also, please don't quote your own text in posts, that's not necessary
FK constraint has been defined correctly. When I see the table relationship for tables using SQL Server 2005 server management studio, both tables have the constraint. I can say its defined both ways. (e.g. Customer & Order, the FK has been defined on Order, pointing to Customer and in Customer table its mentioned that customer id is a primary key on order table)
In Application output window i did not find that designer has ignored any FK constraints.