"Documentation" for purposes of this Agreement shall mean the published and generally available user manuals and documentation that Quest delivers with the Software.ġ.2 Restrictions.
For the purpose of this Agreement, the licensed computer software program(s) downloaded and/or installed pursuant to this Agreement will be referred to as the "Software". The provisions of this Section 1 shall apply to any and all Software, as defined below.ġ.1 Software and Documentation. This Agreement may not be modified except by a writing executed by both parties hereto. In the absence of such an agreement, this Agreement shall constitute the complete and exclusive statement of the terms and conditions and no extrinsic evidence whatsoever may be introduced in any judicial proceeding that may involve the Agreement. The terms and conditions of this Agreement are intended by the parties as a final expression of their agreement with respect to the subject matter hereof and may not be contradicted by evidence of any prior or contemporaneous agreement unless such agreement is signed by both parties. This agreement (the "Agreement") is made between Quest Software, Inc., ("Quest") and you, the customer ("Licensee"). THIS AGREEMENT DOES NOT SUPERSEDE ANY OTHER WRITTEN AGREEMENT BETWEEN YOU AND QUEST SOFTWARE, INC.
IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE. BY DOWNLOADING, INSTALLING OR USING THE SOFTWARE YOU INDICATE ACCEPTANCE OF AND AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT.
ModifiedCreateRelationship.PLEASE READ THIS SOFTWARE LICENSE AGREEMENT CAREFULLY. Message was edited by: vladka - added note If you have any questions, please write us back. It is possible to get to Relationship from its shortcut via property ParentBase (please see the script).Ī third question: How can I make an existing relation visible in a workspace? …Ī) the entity right-click option, Fill Parent and Child Objects (for particular entity)ī) the WS right-click option | Add Selected Objects to Workspace, enable only the Links button and select the relationships of which shortcuts you want to add to the WS.Īlso, it is possible via script - please see it attached. The script returnes just shortcuts of relationships as only shortcuts are on WS. In any case, it’s good to hear you solved the problem.Ī second question: What is the main idea of creating of the relations (foreign keys) between entitites?. What panes/windows were open during the application close? Was there the Scripting Window? Did any error message occur? What did it say? To be able to simulate the problem, we would need more information. I created a new configuration during the installation to stop the problem. To be sure I uninstall the version 3.3.7.22 and installed the version 3.3.8.11. My TDM was very instable at closing of the application. shortcut to all WS where Auto Complete is on and will not add the rel. In any case, the modified script is better - it will add the rel.
Please find attached a new script that fixes this problem. Yes, unfortunately the problem with two shortctuts of relationship occurs on WS where Auto Complete (option in Workspace Format) is on.
It is very difficult in TDM to rich it when I add an existing entity on an existing Workspace, because of the existing relations of that entity. The problem: I want normally show also all relations among the entities on each Workspace. I plan to prepare a script that goes through all workspaces and shows all invisible relations at each of them. How can I make an existing relation visible in a workspace? Of course via script. We get ID of the Workspace where we want to show the relation, we get ID of the both entitites, we create a link and later we search somehow via Model for the corresponding relation and set the properties of it (e.g. What is the main idea of creating of the relations (foreign keys) between entitites? When I select one of the both lines and delete it (and select option Really remove) then it deletes also the second one. The problems at closing of the application don’t happen any more, but the problem with the twice lines between Entity1 and Entity2 remains. (= There was only one line between Entity1 and Entity2 in ‘All Items’.) When I specified another one here, then the problem was again only on the specified workspace, but not on on ‘All Items’.
It happens only in the workspace that I specify in the code line I’ve modified your script (see the attached file CreateRelationshipLada.js).īut, when I run it, the script creates more lines between entitites Entity1 and Entity2.