Could this issue be specific to Excel 2003 ???
 

Hi all, I'd appreciate some advice here. I'm in a bit of a hole!

My program is written in Excel 2002. I'm after being contacted by someone
running Excel 2003, and getting a "Runtime error 9 - Subscript out of range".

I know under normal circumstances what this error means, how to locate it,
and how to fix it. So no problem there. However, I've tested my program over
and over in Excel 2002, and haven't been able to reproduce the problem in the
specific area that he's receiving it (Without doing something blatently
obvious like changing a sheet name that can't have happened to his version).
Anyway, I'm waiting for him to send me his specific files for me to check in
order to investigate further. No-one else has reported this or any problems,
so at this point I'm guessing that its isolated.....which leads me to this
post....

In a previous version of the same program, the only issue I received was
from someone running Excel 2003, and now with my updated program, this issue
is while running Excel 2003.....am I seeing the start of a pattern or just
coincidence?
Is there a history of problems with Excel 2003?
Is Excel 2003 a less reliable build than other Excel versions?
Was there some sort of VBA change between 2002 and 2003 that I'm unaware of?

........any ideas about this in general? I'm not asking for error specific
info since I know you can't help without more information which I can't give
right now.

Thanks.

Could this issue be specific to Excel 2003 ???
 

The only problems I have ever encountered were with Object Library references
and those were easy enough to fix. I am not aware of any inherent problems
related to Subscript Out of Range between xl2000 and xl2003. That was a
fairly seamless transition as far as I know.

"dim" wrote:

Hi all, I'd appreciate some advice here. I'm in a bit of a hole!

My program is written in Excel 2002. I'm after being contacted by someone
running Excel 2003, and getting a "Runtime error 9 - Subscript out of range".

I know under normal circumstances what this error means, how to locate it,
and how to fix it. So no problem there. However, I've tested my program over
and over in Excel 2002, and haven't been able to reproduce the problem in the
specific area that he's receiving it (Without doing something blatently
obvious like changing a sheet name that can't have happened to his version).
Anyway, I'm waiting for him to send me his specific files for me to check in
order to investigate further. No-one else has reported this or any problems,
so at this point I'm guessing that its isolated.....which leads me to this
post....

In a previous version of the same program, the only issue I received was
from someone running Excel 2003, and now with my updated program, this issue
is while running Excel 2003.....am I seeing the start of a pattern or just
coincidence?
Is there a history of problems with Excel 2003?
Is Excel 2003 a less reliable build than other Excel versions?
Was there some sort of VBA change between 2002 and 2003 that I'm unaware of?

.......any ideas about this in general? I'm not asking for error specific
info since I know you can't help without more information which I can't give
right now.

Thanks.

Could this issue be specific to Excel 2003 ???
 

The short answer is yes - The versions from one to another do vary. I
have a sort routine which is not backwards compatible from 2003 to
2000 for instance.

Even the the same excel family (Excel 2003) has different builds
(service packs) which can vary the behaviour.



dim wrote:
Hi all, I'd appreciate some advice here. I'm in a bit of a hole!

My program is written in Excel 2002. I'm after being contacted by someone
running Excel 2003, and getting a "Runtime error 9 - Subscript out of range".

I know under normal circumstances what this error means, how to locate it,
and how to fix it. So no problem there. However, I've tested my program over
and over in Excel 2002, and haven't been able to reproduce the problem in the
specific area that he's receiving it (Without doing something blatently
obvious like changing a sheet name that can't have happened to his version).
Anyway, I'm waiting for him to send me his specific files for me to check in
order to investigate further. No-one else has reported this or any problems,
so at this point I'm guessing that its isolated.....which leads me to this
post....

In a previous version of the same program, the only issue I received was
from someone running Excel 2003, and now with my updated program, this issue
is while running Excel 2003.....am I seeing the start of a pattern or just
coincidence?
Is there a history of problems with Excel 2003?
Is Excel 2003 a less reliable build than other Excel versions?
Was there some sort of VBA change between 2002 and 2003 that I'm unaware of?

.......any ideas about this in general? I'm not asking for error specific
info since I know you can't help without more information which I can't give
right now.

Thanks.

Could this issue be specific to Excel 2003 ???
 

Thanks folks......two different replies, two different answers! :-) lol

So is there information anywhere on what differences need to be accounted
for when writing VBA in 2002 for different versions?

Cheers.

Could this issue be specific to Excel 2003 ???
 

Is there a history of problems with Excel 2003?
Is Excel 2003 a less reliable build than other Excel versions?

No disrespect intended but don't rule out the possibility there is a problem
with the code that only obscure circumstances bring out.

--
Jim
"dim" wrote in message
...
| Thanks folks......two different replies, two different answers! :-) lol
|
| So is there information anywhere on what differences need to be accounted
| for when writing VBA in 2002 for different versions?
|
| Cheers.

Could this issue be specific to Excel 2003 ???
 

Just a note...

xl2002 (IIRC) added a DataOption# parm to the range.sort method. If you want
the code to work in xl2k (and you don't care about that parm), you can delete it
from the code.

Greg Glynn wrote:

The short answer is yes - The versions from one to another do vary. I
have a sort routine which is not backwards compatible from 2003 to
2000 for instance.

Even the the same excel family (Excel 2003) has different builds
(service packs) which can vary the behaviour.

dim wrote:
Hi all, I'd appreciate some advice here. I'm in a bit of a hole!

My program is written in Excel 2002. I'm after being contacted by someone
running Excel 2003, and getting a "Runtime error 9 - Subscript out of range".

I know under normal circumstances what this error means, how to locate it,
and how to fix it. So no problem there. However, I've tested my program over
and over in Excel 2002, and haven't been able to reproduce the problem in the
specific area that he's receiving it (Without doing something blatently
obvious like changing a sheet name that can't have happened to his version).
Anyway, I'm waiting for him to send me his specific files for me to check in
order to investigate further. No-one else has reported this or any problems,
so at this point I'm guessing that its isolated.....which leads me to this
post....

In a previous version of the same program, the only issue I received was
from someone running Excel 2003, and now with my updated program, this issue
is while running Excel 2003.....am I seeing the start of a pattern or just
coincidence?
Is there a history of problems with Excel 2003?
Is Excel 2003 a less reliable build than other Excel versions?
Was there some sort of VBA change between 2002 and 2003 that I'm unaware of?

.......any ideas about this in general? I'm not asking for error specific
info since I know you can't help without more information which I can't give
right now.

Thanks.

--

Dave Peterson

Could this issue be specific to Excel 2003 ???
 

"Jim Rech" wrote:
No disrespect intended but don't rule out the possibility there is a problem
with the code that only obscure circumstances bring out.

None taken. If I could fine an error it would make everything much
easier....I could just fix it!

I haven't used that Range.sort method so I don't think it'd be
related.....thats if I'm understanding you right....

Thanks folks. I guess without being able to replicate the error I just have
to let it go and keep an eye out for it in future.

Thanks again.