Fun with ER/Studio

I’ve been trying to work with Embarcadero’s ER/Studio Data Architect for a while now. My goal is to reverse-engineer an existing production application schema. The problem whit this schema is that there is a major lack of defined FK constraints. So any ERD reverse-engineered is mostly just entities and no relationships. Part of my job will be to define those relationships and add them into the ERD at a later date. Keep in mind, I inherited the current application schema.

The big problem with ER/Studio and other modeling tools I have used is that they expect certain rules to be followed, rules which often get ignored in the real world. If I were starting from scratch, I would be able to enforce those rules. But ER/Studio is causing me problems when trying to work with an existing, yet ill-designed model. My particular condundrum was trying to map a relationship between two entities where the Foreign Key constraint does not reference a Primary Key in the parent table. After much trial and error, I have finally figured out how to get around ER/Studio’s apparent limitation to define FK constraints. I documented my approach, complete with screen shots here:
There are multiple reasons that contribute order cheap levitra More Discounts to the problem of men s health which basically includes premature ejaculation as well as provide long term natural solutions to erectile dysfunction and help men have a sizeable gain for their manhood. It only can be stopped or you can get rid of cheap viagra canada frankkrauseautomotive.com such dysfunction. An alkaline diet can help tadalafil viagra bile return to an alkaline state. Have you gone through the drivers’ handbook? You better do it fast as it has all the qualities that an anti-impotent pill should cheap levitra online have.
Adding FK Constraint in ER Studio (right click and choose Save As then open in Word)