Customers are reporting issues when sending documents created in Excel 2003
to those with 2000. They are unable to use the macros. It is not an issue
of security settings--all are set to medium. A user said they heard there
was a way to create a macro in 2003 that is "saved as" 2000. Aside from
issues with features in 2003 not in 2000, does anyone have any knowledge or
experience with this issue?

Thanks,
Lori

Hi Lori,
I also have some customers whose 2003 macros error out on 2000 machines. For
me it has always been an issue revolving around 2003 features not in 2000.
The only one that comes to mind immediately is the Workbooks.OpenText
Filename:=....
function. In 2003 you can add an argument at the end that tells Excel to
treat trailing minuses on values as negative numbers. Version 2000 does
recognize this argument. Also in this function the Origin:= part can contain
code after the = sign that will make the macro bomb in 2000.
By finding where the code errors out, I have been able to fix the macro so
it would be 2000 compatible.

--
Ken Hudson


"Lori Smith" wrote:

Customers are reporting issues when sending documents created in Excel 2003
to those with 2000. They are unable to use the macros. It is not an issue
of security settings--all are set to medium. A user said they heard there
was a way to create a macro in 2003 that is "saved as" 2000. Aside from
issues with features in 2003 not in 2000, does anyone have any knowledge or
experience with this issue?

Thanks,
Lori

Thanks for the info. Dumb question . . . how have you been able to figure
out specifically where it is erroring? Is there a way to step through the VB?

Thanks!
Lori

"Ken Hudson" wrote:

Hi Lori,
I also have some customers whose 2003 macros error out on 2000 machines. For
me it has always been an issue revolving around 2003 features not in 2000.
The only one that comes to mind immediately is the Workbooks.OpenText
Filename:=....
function. In 2003 you can add an argument at the end that tells Excel to
treat trailing minuses on values as negative numbers. Version 2000 does
recognize this argument. Also in this function the Origin:= part can contain
code after the = sign that will make the macro bomb in 2000.
By finding where the code errors out, I have been able to fix the macro so
it would be 2000 compatible.

--
Ken Hudson


"Lori Smith" wrote:

Customers are reporting issues when sending documents created in Excel 2003
to those with 2000. They are unable to use the macros. It is not an issue
of security settings--all are set to medium. A user said they heard there
was a way to create a macro in 2003 that is "saved as" 2000. Aside from
issues with features in 2003 not in 2000, does anyone have any knowledge or
experience with this issue?

Thanks,
Lori

In my cases, the macro starts and then it "breaks" at the bad code and
highlights the stopping place. I ask the user to read the code to me and then
I research it.
It doesn't happen that way for you?
--
Ken Hudson


"Lori Smith" wrote:

Thanks for the info. Dumb question . . . how have you been able to figure
out specifically where it is erroring? Is there a way to step through the VB?

Thanks!
Lori

"Ken Hudson" wrote:

Hi Lori,
I also have some customers whose 2003 macros error out on 2000 machines. For
me it has always been an issue revolving around 2003 features not in 2000.
The only one that comes to mind immediately is the Workbooks.OpenText
Filename:=....
function. In 2003 you can add an argument at the end that tells Excel to
treat trailing minuses on values as negative numbers. Version 2000 does
recognize this argument. Also in this function the Origin:= part can contain
code after the = sign that will make the macro bomb in 2000.
By finding where the code errors out, I have been able to fix the macro so
it would be 2000 compatible.

--
Ken Hudson


"Lori Smith" wrote:

Customers are reporting issues when sending documents created in Excel 2003
to those with 2000. They are unable to use the macros. It is not an issue
of security settings--all are set to medium. A user said they heard there
was a way to create a macro in 2003 that is "saved as" 2000. Aside from
issues with features in 2003 not in 2000, does anyone have any knowledge or
experience with this issue?

Thanks,
Lori