Hi,

What are the changes I have to deal with when I upgrade from Excel 2000 to
2003?
Will my Excel 2000 sheet, with macros and VBA, work without any problems in
2003? Is there any information from Microsoft what has to be changed in
macros or VBA code?
Any helpy appreciated.

Cheers
René

Most of the changes should not be visible. You may have to re-enter some of
you custom settups, like which menu bars are open for use, etc.
--
Gary's Student


"Rene H" wrote:

Hi,

What are the changes I have to deal with when I upgrade from Excel 2000 to
2003?
Will my Excel 2000 sheet, with macros and VBA, work without any problems in
2003? Is there any information from Microsoft what has to be changed in
macros or VBA code?
Any helpy appreciated.

Cheers
René

Most of the problems with migration occur when you go backwards to an older
version. Microsoft attempts to accomodate code from past versions (back to
97 I believe). But, as they include new functionality in the newer versions,
things you do with 2003 might not work with older versions.

"Rene H" wrote:

Hi,

What are the changes I have to deal with when I upgrade from Excel 2000 to
2003?
Will my Excel 2000 sheet, with macros and VBA, work without any problems in
2003? Is there any information from Microsoft what has to be changed in
macros or VBA code?
Any helpy appreciated.

Cheers
René

I just came across 2 whitepapers from Microsoft that cover Office 2003
migration issues.

2000 - 2003:
http://whitepapers.silicon.com/0,390...000588q,00.htm
XP - 2003:
http://whitepapers.silicon.com/0,390...000588q,00.htm

One point in of of the whitepapers that I found especially interesting
was their recommendation to use late binding. In the past I've heard
(and have repeated to others) that you can just reference the object
library of the oldest version that you plan to support (typically Excel
2000). According to the whitepaper, though, doing so can still lead to
some forward compatibility issues.

Nick Hebb
BreezeTree Software
http://www.breezetree.com