Important information for you.
1. TDM3 issue
I sent a note to my support contact at Quest to get TDM3.
As I wrote previously, BETA version of TDM3 is only available. This modeling community is a place where you can discuss TDM3 issues and join the TDM3 BETA testing program.
Please read information on the BETA program at:
Also, let me quote this:
Toad Data Modeler 3 BETA is supported ONLY via this community directly by our Development team. Quest Software Support team does NOT provide any support to the BETA. All your questions and requirements should be sent to: firstname.lastname@example.org or published in our Discussion Forum.
You can download BETA from:
2. To your trouble with TDM2 2.25 - foreign keys
…there are bugs in this version and this does not work.
I’m not sure what bugs you mean. Let me explain how TDM works:
As soon as you create an identifying relationship, Toad Data Modeler automatically adds a copy of the primary key of the Parent table to the Child table - Primary Foreign Key (PFK). (The foreign key in Child table is a part of the primary key.)
As soon as you create a non-identifying relationship, Toad Data Modeler automatically adds a copy of the primary key of the Parent table to the Child table - Foreign key (FK). (This foreign key in Child table is not a part of the primary key.)
In other words, foreign keys (PFKs and FKs) are imported from parent entities to child entities automatically while creating relationship. Foreign keys cannot exist without relationships. Therefore, you are not allowed to delete FK or PFK from Child tables either. To delete them, you have to delete appropriate relationship.
* What can happen after RE…
You have reverse engineered a model without relationships. In TDM, a new model has been created. However, information about foreign keys has been lost as in TDM stands that foreign keys cannot exist without relationships.
You have created a new relationship and so new foreign key has been added to the child entity automatically. Now the child entity has two attributes of the same name (the original attribute and the newly added foreign key).
Solution: Foreign Keys Mapping
Sources of Info:
Well, I hope this information will clarify this problem a bit.
Anyway, I suggest to discuss the problem with TDM 2 outside this community. Possibly, the problem is anywhere else. Please contact me via email@example.com with your questions and detailed description of your problem. You can also send us your model. Our TDM team will check it out.
Message was edited by: vladka