Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Follow-up
Topic Summary: Follow-up RE: Partition from 7 rejoin in 8
Created On: 28-Mar-2006 01:07
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 28-Mar-2006 01:07
User is offline View Users Profile Print this message


Don Fowler

Posts: 12
Joined: 28-Jun-2005

To recap: I created a partition of a module in DOORS 7 and a few weeks later moved to 8. Our Customer, still on 7, sent the rejoin back. I obtained a recent backup of the database before the migration to 8, open it in 7, and rejoined the partition. I then achived the module and imported that into DOORS 8. This was successful, however, I now have a different related problem: what to do about the repartition... A couple of possibilities come to mind: 1. I could repartition the module in 7, send this back to the customer, at the same time create a partition of the same module in DOORS 8 using the same partition definition and throw it away (so they could continue to work in DOORS 7), and wait for them to go to 8 at which time they could send me a synchronize file which I could (I hope!) synchronize in 8.0. 2. I could archive the module in 7 and send that to them and do nothing to the module which I rejoined and migrated to 8, because after they migrate to 8 I would have to import an archive of their module which would wipe out anything I might have done to their module. of course if 1. doesn't work I am left with a module which I cannot rejoin the away database partition to and regain write access to and a partition which has no home database. Oh, what tangled webs we weave, When we first practice to receive (a partition). Appologies to Sir Walter Scott Don Fowler L-3 Communications Systems Engineer
Report this to a Moderator Report this to a Moderator
 28-Mar-2006 17:35
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

If you are not modifying this customer module at all in your DB, then you could forget about deceiving the receiving of your partition contriction and awaiting the oration of their migration, and just periodically purge your copy and restore an archive of their's. Deny MCD access to your copy.

KISS: Keep it Simple Stupid.

- Louie
Report this to a Moderator Report this to a Moderator
 28-Mar-2006 19:58
User is offline View Users Profile Print this message


Don Fowler

Posts: 12
Joined: 28-Jun-2005

Hi, Louie Sorry, I didn't make it clear what I was trying to accomplish here. I am using the partition-synchronize functionality to receive textual information from the customer. The con-textual information is created through links to the module. The away database module is MCD while the home is Read-only. I will be creating context through links to the periodically synchronized module, while the customer continues to add information to the away module. The problem with archive-restore would be that the links would be destroyed each time the module is reatored and would have to be saved, deleted and reatored each time the module is restored to the "home" database. not that I can't do that, it is kind of a pain to do with such a neat tool as the partition-synchronize avalable. Don
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.