Dave,

Yeah, I agree that IE should not be opening the Excel file. Thank you for
the feedback, the article was definitely helpful!

Mark

"Dave Peterson" wrote:

This may not be a good solution for you...

I'd do my best to not let MSIE open the file:

How to Configure Internet Explorer to Open Office
Documents in the Appropriate Office Program Instead of in Internet Explorer
http://support.microsoft.com/?scid=162059

There are just too many things that don't work when an excel file is opened in a
browser.

peabrain25 wrote:

Thanks, p45. No, I just threw some arbitrary names for sheets in the quotes.
One tab is actually called "Write - Off", etc.

I think we figured out part of the problem. Users are linking to the form
through a web portal which is now causing the form to open within Internet
Explorer. When it is opened through Excel there doesn't seem to be any
problems, but when it has the IE background it doesn't seem to work. So this
is a whole new problem...

Thanks,
Mark

"p45cal" wrote:

I notice that your statements below include a space between the word 'Sheet'
and its number. On my excel 2003 there is no space. Could it be that the
upgrade has changed the names of the sheets?
--
p45cal


"peabrain25" wrote:

Hello,

Our company is in the process of upgrading from Office 2002 to Office 2003.
We are encountering a problem with some of our Excel macros. The workbook is
set up with a variety of different request forms, each on its own tab. There
are several shortcut buttons to jump from form to form. Each of these
shortcuts has VB code behind it that simply says:

Sheets(€œSheet 1€�).Activate
Sheets(€œSheet 2€�).Activate
Etc.

All of these still work fine. The problem is that the same code doesn€„¢t work
when it is called from a userform. When the user clicks a button, for
example, the macro successfully runs and the userform is shown. All the
buttons on the form work except for one which bombs on the statement:

Sheets(€œSheet 1€�).Activate

I tried using a .Select statement instead but that also did not work.
Everything works well in Office 2002, but for some reason after the upgrade,
this consistently bombs in 2003. Has anyone else encountered this, or have
any ideas for a fix?

Thanks,
Mark


--

Dave Peterson