![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL compatibility between 5.2 and 7.1 (new to dxl) Topic Summary: Created On: 10-Jul-2006 08:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi everyone
The firm I'm working for is planning to move from version 5.2 of Doors to 7.1. One of the things that worries me at the moment is what the differences might be in the dxl code used between 5.2 and 7.1. We operate allot of customised scripts for things like configuration management, and interrogating data. Is there any way/tool that is available that can scan scripts and determine incompatibilities? Or am I better to go-ahead with the migration and fix any scripts as they break? Many thanks for any help ![]() David Carroll |
|
![]() |
|
![]() |
|
Definately the later option. You wont find too many incompatabilities as the DXL is essentially backwards compataible. If you have the resources perhaps even try setting up a test copy of your database under 7.1 and testing your scripts out before you make the switch.
------------------------- Kim Faint (kim.faint@boeing.com) Systems Engineer Boeing Australia http://www.boeing.com.au |
|
![]() |
|
![]() |
|
David,
A significant change from DOORS 5.x to DOORS 6.x is the storage of OLE objects. In DOORS 6.x and above, if OLE objects appear in the DOORS "main" column, they are embedded in the "Object Text", where in DOORS 5.x they were not. The issue will be important if you have any DOORS 5.x scripts that programatically manipulate "Object Text". If so, the scripts should be modified to be aware of OLE objects. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
He means "... manipulate any attribute of type 'Text'..."
If your scripts never set Object Text ..err.. I mean never set any Text attribute and your reports only retrieve raw text (ignoring all formatting), then it won't matter. If your scripts dealt with OLE diagrams at all, other than using "oleIsObject" (which now means 'any OLE in Object Text'), then they will need to be rewritten: the notion of "the" OLE in the object is no longer valid, rather you need to find individual OLEs in the Text Attributes. Telelogic keeps them for 'backwards compatibility', but should suppress these perms; "oleDelete(obj)" used to mean "delete 'the' OLE in the object"; but what does it mean now that you can have lots of OLEs in lots ot Text attributes? I think it now means "trigger undeciferable run-time errors". I think it extremely odd that the new OLE commands deal with the Column instead of the attribute reference. - Louie |
|
![]() |
|
![]() |
|
Thankyou very much everyone for your replies
![]() I havent written all of the scripts on this installation myself, so I think the action I will take is to see if I can get the resource for a test database ahead of time. Thanks David |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.