Re: How to compare project versions when source project is not sam
- From: "Rick Williams" <onetruerick@xxxxxxxxxxxxx>
- Date: Tue, 14 Mar 2006 18:26:34 -0600
I wrote a similar macro years ago, in which the user specified the "common"
field. I could probably dig it up if anyone needs it.
Rick Williams
non-MVP
"John" <mjensen@xxxxxxxxxxxx> wrote in message
news:mjensen-A72CED.15143014032006@xxxxxxxxxxxxxxxxxxxxxxx
In article <F5F3DF5F-032D-4E78-97E8-0398A8E8CBC2@xxxxxxxxxxxxx>,
John Primavera <JohnPrimavera@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi John,
They do have elements from a common origin, but not from Projectâ?¦
We have an Access DB with project info, and we export to Project to
obtain
the Gantt view. We originally considered the Project file only as a
â?oreport
displayâ??, but then thought it would be useful to also see project info
changes graphically. We thought we could save generated Project files as
â?osnapshotsâ?? and then compare versions. The compare project versions
add-in
does exactly what we want but wonâ?Tt work for us because the Project
file is
re-created each time from the Access DB whenever we want an updated Gantt
view.
Any suggestions would be appreciated!
John,
OK, I understand your process although if you are doing any serious
planning & scheduling, I suggest you learn more about Project and use it
as the main application. Project is of course also a database but one
that is customized as a planning/scheduling application. I wouldn't go
so far as to say that it is an injustice to use Project strictly for its
Gantt capability but it does have a whole lot more to offer.
With regard to your compare issue. Several years ago I wrote a couple
versions of a compare macro for Project files. That was before MS
released their Compare Project Versions utility/add-in. My original
macro used the Unique ID as an index for comparing but I also developed
a macro that used another user designated field. It was primarily
intended for master projects with inserted subprojects since the Unique
ID scheme gets a little dicey in that situation. I never really
completed the code but based on my experience, it is possible to develop
a utility that would compare two "semi-related" Project files. The
process would be easier if only a limited number of fields were being
compared.
Other than that I don't have any suggestions
John
Project MVP
"John" wrote:
In article <232B177F-2AAB-4D4C-AF8D-0DBCBA8F6439@xxxxxxxxxxxxx>,
John Primavera <John Primavera@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am able to run the compare project versions add-in for Project 2002
when
the source project is the same, i.e., a file compared against a
modified
copy
of the same file. When I try to run it on two files that have very
similar
or even the same contents, but that do not come from the same
original
file,
all tasks from both files are flagged as changes. Itââ,¬â"¢s as if
thereââ,¬â"¢s
a
behind-the-scenes unique identifier that is used to match tasks,
which
will
never match up unless the files compared come from the same original
file.
So, is there a way to compare project versions when the source
project is
not
the same?
John,
The "behind the scenes" unique identifier is exactly that, the Unique
ID
field. Is there a way to compare two Project files that don't have the
same ancestry? Perhaps, but it would require a complex compare
algorithm
- not something that can be done casually.
Just a question but why would two files be comparable if they don't
have
elements from a common origin?
John
Project MVP
.
- Follow-Ups:
- Re: How to compare project versions when source project is not sam
- From: John Primavera
- Re: How to compare project versions when source project is not sam
- References:
- Prev by Date: Re: Does Resource Pool Hold Old Data?
- Next by Date: Re: Automatic calculation w/ add duration to "planned start/finish
- Previous by thread: Re: How to compare project versions when source project is not sam
- Next by thread: Re: How to compare project versions when source project is not sam
- Index(es):
Relevant Pages
|
