Comparing Versions - Error Messages

I am having a lot of trouble using the add-in Compare Versions utility. I get error messages and then the macro stops working. By the way, I use a lot of custom fields, and I found by experimentation that when I remove all the customizations the Compare Versions utility is much more likely to run properly, but even then I sometimes get errors that cause the compare to fail.

One error pops up as "Run-time error '424': Object required", and offers just an "OK" button for response. When "OK" is pressed, I get a box saying "An error occurred in the COM Add-in named: Compare Project Versions Utility Error #:0".

Another error pops up as "Run-time error '1101': The argument value is not valid." Once again this leads to the second box, as above.

Is there any help file available that enumerates these error messages, giving some clue as to their cause and better yet, to their resolution? Also, does anyone know who wrote this utility, and whether they will accept questions from users?

With thanks in advance,

David Hunsberger
www.it7.com

David,
Sorry you are having so much trouble with the Compare Project versions
add-in. I didn't write the add-in code but I did write a similar VBA
macro and have a good idea of how the add-in works. First, are you
working with a single file structure? That is, the files to be compared
connot be consolidated (master with inserted subprojects). Second, do
you duplicate any fields in the view table? The add-in code will
generate a run time error if for example, your view table shows the
Start field more than once. The error will occur even if the Start field
is hidden. I suggest you go to View/Table/More Tables and hit "edit".
Look through the field names and make sure there are no duplicates.
Delete any duplicate fields.

I don't know how the add-in reacts to custom fields. I've never tried it
but it is possible that one or more of the formulas could be causing a
problem when the add-in code attempts to perform a field cell compare.
If at all possible I suggest you set up a view table that does not
contain any custom fields and run the compare.

Let me know what happens. We can get you something that works, one way
or another.

John

Hi John -- thanks for the thoughts. I believe I did none
of the things you mention: I used a flat single file in
two versions, not a consolidated project and with no
inserted projects. The table used in the compare was a
default "entry" table with the default columns, no custom
columns and no hidden columns (I checked with edit
table). As someone who has written VBA can you parse the
original error messages to get a sense what kind of errors
they are? I have no clue. Thanks again, David Hunsberger
>-----Original Message-----
>
>David,
>Sorry you are having so much trouble with the Compare
Project versions
>add-in. I didn't write the add-in code but I did write a
similar VBA
>macro and have a good idea of how the add-in works.
First, are you
>working with a single file structure? That is, the files
to be compared
>connot be consolidated (master with inserted
subprojects). Second, do
>you duplicate any fields in the view table? The add-in
code will
>generate a run time error if for example, your view table
shows the
>Start field more than once. The error will occur even if
the Start field
>is hidden. I suggest you go to View/Table/More Tables and
hit "edit".
>Look through the field names and make sure there are no
duplicates.
>Delete any duplicate fields.
>
>I don't know how the add-in reacts to custom fields. I've
never tried it
>but it is possible that one or more of the formulas could
be causing a
>problem when the add-in code attempts to perform a field
cell compare.
>If at all possible I suggest you set up a view table that
does not
>contain any custom fields and run the compare.
>
>Let me know what happens. We can get you something that
works, one way
>or another.
>
>John
>.
>

David,
Ok, given the files you are trying to compare are benign (i.e. single
file using the default Entry table), tell me again what error message(s)
you get.

I have found that most error messages are quite cryptic. They are
probably of necessity rather generic and apply to more than one specific
problem. As you have probably found, hitting the button for more
information generally gives 2 or 3 different causes, none of which makes
much sense unless you already have an idea of why you got the message in
the first place. This is where experience comes in.

I have a couple more suggestions. If the add-in still chokes on your
benign file, try reloading the add-in. If that still fails, would it be
possible to e-mail me the files so I can take a look at them? If the
files contain sensitive information, I can provide you a macro that will
remove that information or you can get a similar macro called "scrub" by
going to Jack Dahlgrens webpage at:
http://masamiki.com/project/macros.htm
If both the original and revised files are de-sensitized with the same
macro the compare add-in should still work fine.

John

John -- Thanks for all your care with this problem. I am
emailing you directly some screen shots of the error
messages, in Word docs. If you see anything
understandable, feel free to answer here in the forum.

-- David Hunsberger

>-----Original Message-----
>
>David,
>Ok, given the files you are trying to compare are benign
(i.e. single
>file using the default Entry table), tell me again what
error message(s)
>you get.
>
>I have found that most error messages are quite cryptic.
They are
>probably of necessity rather generic and apply to more
than one specific
>problem. As you have probably found, hitting the button
for more
>information generally gives 2 or 3 different causes, none
of which makes
>much sense unless you already have an idea of why you got
the message in
>the first place. This is where experience comes in.
>
>I have a couple more suggestions. If the add-in still
chokes on your
>benign file, try reloading the add-in. If that still
fails, would it be
>possible to e-mail me the files so I can take a look at
them? If the
>files contain sensitive information, I can provide you a
macro that will
>remove that information or you can get a similar macro
called "scrub" by
>going to Jack Dahlgrens webpage at:
>http://masamiki.com/project/macros.htm
>If both the original and revised files are de-sensitized
with the same
>macro the compare add-in should still work fine.
>
>John
>.
>