I have essentially completed the task of reverse engineering 12 standard schemas in our database with TDM. I would like to share some observations.
When you close/open models, some print settings are not saved. Particularly
this applies to “Print page number” and “Print frame”. There may be others.
When you Reverse Engineer or Update the model of a schema, you get a whole
series of messages. Many of those messages do not apply (Not being selected
for RE). The message should say so. Also the last is “Reversing triggers…”.
The program halts here for a long time. I think it moves onto a new state
and should say something like “Processing…”.
Whenever I print many of the models, "I get the message “The margins are set
outside of printable are of the page. Do you want to continue?”. First, are
should be area. If I select Yes, the model appears to print OK. Besides the
obvious, what does the message indicate? Details, please.
Maybe I don’t have my grid settings right, but I get small kinks in FK lines that I
can’t get rid of by shifting an entity slightly. Trying to delete handle points does
Why are there workspace settings under Options->Physical Model and under
Workspace Format off the right click menu of the Workspace? I see no reason
for the duplication of many of the settings like for fonts.
I have at least one model with the grid off, but the grid dots still are present.
Provide a way to “anchor” notes and text to an entity, such that when an entity is
moved, the note or text moves with it.
I have expressed previously my disappointment with the FK line drawing
algorithm of TDM. I have several suggestions for improvement. These may or
may not apply outside of using “Right angles”.
a) Never pass through an entity. Go around it. I find this particularly true when I
move one entity from one side of an entity, the FK line may remain fixed to
the other side. With a little finagling, you can get it to move, but TDM seems
to have no rhyme or reason for what it does. You just keep trying until you
get what you want.
b) Straight lines should be used where ever possible, even if the entity being
moved must be shifted somewhat. The latter is because the anchors to the
parent are automatically redistributed after adding an anchor to a side.
c) When parent/child entities have 2 relationships, I have problems with them
crossing each other rather than being separated after moving the child
d) You may what to rethink the even distribution of anchors on a side. It may
look nice, but it causes lines to shift unexpectedly and other problems.
e) Along with d), you should be able to move an anchor. That would fix some of
issues with a).
Thanks in advance for any feed back,