Comparing Versions - Error Messages

[David Hunsberger]

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 Hunsberge
www.it7.co

 

[John]

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