Merging Two Files
in [Project]
|
From: Michozzy on 27 Apr 2010 00:06 Hi, I am getting ready to marry up two schedules (around 6000 task lines) and am trying to find a potentially quicker solution than what I have planned (just in case plan A doesn't go so well for me). Two months ago I took a copy of my master file and began to add much needed work into it, however it was not yet authorized work, so I had to continue providing status into the main master file up to this point in time. Now that the work will be authorized in May, I need to take the current master file, and make sure all of the "what-if" modifications from the secondary file get into it. I am planning to have a partner help me with this, as my second set of eyes. Would you guess that the easiest way to do this would be to literally go line by line to make sure we get all of the "revised" logic in? The UIDs are not a one-for-one deal (in other words, many task name changes, cost changes, logic changes, etc) have switched around in my "what-if". Are there any suggestions for an easier way to compare the two files? I am well aware of the file-compare tool, and my company has created a more sophisticated bolt-on version of it, but other than that, any other suggestions to make sure we don't waste too much precious time? We have about eight days to conquer this beast. Thanks so much!
From: Rod Gill on 27 Apr 2010 01:36 If the Unique IDs have remained the same, then VBA code could quickly update task names, and resource assignments etc. If Unique IDs have changed you could try inserting a custom Number and entering the Unique ID of the same task in the other file and again have a VBA macro to read task data using the ID in the number field. This would be easy and straight forward for anyone with basic VBA skills (or talk to me!). Essentially for any kind of successful merger there has to be a common field for Project or a VBA macro to use. If you don't have a reliable merge field it's probably back to the old mark 1 manual methods and I don't envy you that for 6,000 tasks! -- Rod Gill Microsoft MVP for Project - http://www.project-systems.co.nz Author of the only book on Project VBA, see: http://www.projectvbabook.com "Michozzy" <Michozzy(a)discussions.microsoft.com> wrote in message news:DDCBF777-F0EC-4F32-B282-18F01366BA56(a)microsoft.com... > Hi, I am getting ready to marry up two schedules (around 6000 task lines) > and > am trying to find a potentially quicker solution than what I have planned > (just in case plan A doesn't go so well for me). > > Two months ago I took a copy of my master file and began to add much > needed > work into it, however it was not yet authorized work, so I had to continue > providing status into the main master file up to this point in time. > > Now that the work will be authorized in May, I need to take the current > master file, and make sure all of the "what-if" modifications from the > secondary file get into it. I am planning to have a partner help me with > this, as my second set of eyes. Would you guess that the easiest way to do > this would be to literally go line by line to make sure we get all of the > "revised" logic in? The UIDs are not a one-for-one deal (in other words, > many > task name changes, cost changes, logic changes, etc) have switched around > in > my "what-if". Are there any suggestions for an easier way to compare the > two > files? > > I am well aware of the file-compare tool, and my company has created a > more > sophisticated bolt-on version of it, but other than that, any other > suggestions to make sure we don't waste too much precious time? > > We have about eight days to conquer this beast. Thanks so much! > > > __________ Information from ESET Smart Security, version of virus > signature database 5063 (20100426) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > __________ Information from ESET Smart Security, version of virus signature database 5063 (20100426) __________ The message was checked by ESET Smart Security. http://www.eset.com
|
Pages: 1 Prev: Scheduling one task that is dependent on another Next: Baseline updating |