OK so you are sure the project t.b. updated is not calling the code in
another project to do the update. Are you really sure, reason for asking is
I'm surprised it was not already 100% known for sure without having to go
and check, as it appears you had to do.

I'm afraid scan reading the code below does not give any clues. The updated
code in the adjacent post is 8-900 lines many of which are wrapped. It would
take a long time to reconstruct. And probably much longer to get a feel for
what it all does (out of context)

Some things to try -

Paste what you think is the correct code into the module in the project t.b.
updated.

Update a module in a dummy project (just the suspect module), using code to
do the update, is the new code as it should be.

Working with the actual project t.b. updated, put a break in the code after
it has done the 95% that works fine, then step through the rest with F8.

If the update code is "totally in a separate project, and not called from
the project t.b. updated, I sort of suspect the problem will relate to
something obvious. Just need to see it in the wood amongst the trees.

Regards,
Peter T


"Matt" wrote in message
...
I was thinking along the same lines as far as where the call to update
the code initiated. And to ensure its independence, I created a menu
item that calls the Updater add-in when clicked. The Add-In is given
a reference to the workbook to updated when the workbook to update is
opened. So... the code that is being executed is not contained within
the updating workbook at all. Here's my updating code:
<snip