VBA Macro Issues after 2000 to 2003 upgrade

[Susan G.]

A few years ago I wrote templates for Microsoft Word and Excel containing vba
code. The macros are used to search through designated word files, suck out
particular bits of information, export that info to excel, and create
cross-reference tables in Excel with that info. We use these templates a lot
in my group.
A few weeks ago I got a new laptop with Windows XP (instead of 2000) and
Office 2003 (instead of 2000). I just tried using these macros for the first
time since the upgrade, and I'm running into a lot of problems:
1) The Word macro that exports data to Excel runs EXTREMELY slowly -- it
takes 5 minutes where it used to take 30 seconds. And that's if I save the
file locally; over the network, I give up before I see anything happening.
2) Workbooks made from the Excel template have code to create a menu with
buttons to run the macros. These menus never appear.
3) If I run the macros in Excel, I get an error at the following line,
probably because the menu isn't there:
If CommandBars(sortReqToolBarName).Visible = True Then

Any advice is appreciated. I'm not even sure if this is the correct
forum, so advice on where to go for help is also appreciated. I will also
post in the Word programming forum.

Thanks very much,
Susan

 

[NickHK]

The differences between those 2 versions of Excel are minimal. From what you
have said, no reason to suspect the versioning is the cause, rather
something to do with the setup/installation.
#1 No way to tell without code, but could be a configuration issue.
#3 would be related to #2. Show the relevant code for #2.

NickHK

 

[Susan G.]

Hi NickHK,
Thanks for the post:

#1 No way to tell without code, but could be a configuration issue.

What do you mean by "configuration issue"? You mean something that is set
during installation of the office suite? Or something I can change through
the app?

#3 would be related to #2. Show the relevant code for #2.

Ummm... 2 and 3 are working now -- I'm seeing the toolbar and the code
doesn't get stuck there. I don't know why it wasn't working yesterday and it
works today. I am seeing other problems, though -- for example, my
conditional formatting formula now looks to the row after instead of the
current row. I can go through and debug, although I don't know why the
behavior changed with the upgrade.

Thanks,
Susan