F
F*SH
Hi all
I recently dug up a 2-year-old spreadsheet script of mine, writte
originally in VBA for XL2000. It works fine if I run it under XL2000
but as soon as I try it with the next version of Excel, XL2003,
peculiar error appears.
After a certain point in the code, any VB calls to the spreadshee
fail. this includes all cell reading, writing, chart selection the lot
Any interaction, it seems, returns the 'Application-defined o
Object-defined' error. The point at which this error starts to appea
is when an add-in object that issues callbacks is activated - th
errors seem to stop when this object is deactived (I say 'activation'
this is when the object is set to listen for an external trigger o
sorts. I'm a little hazy on how it works tbh).
A slightly vague question, perhaps, but I'm told this is a common issu
(that said, it's not appearing in my searches). I would blame the add-i
object if it weren't for the fact this script works perfectly in XL2000
Any ideas
I recently dug up a 2-year-old spreadsheet script of mine, writte
originally in VBA for XL2000. It works fine if I run it under XL2000
but as soon as I try it with the next version of Excel, XL2003,
peculiar error appears.
After a certain point in the code, any VB calls to the spreadshee
fail. this includes all cell reading, writing, chart selection the lot
Any interaction, it seems, returns the 'Application-defined o
Object-defined' error. The point at which this error starts to appea
is when an add-in object that issues callbacks is activated - th
errors seem to stop when this object is deactived (I say 'activation'
this is when the object is set to listen for an external trigger o
sorts. I'm a little hazy on how it works tbh).
A slightly vague question, perhaps, but I'm told this is a common issu
(that said, it's not appearing in my searches). I would blame the add-i
object if it weren't for the fact this script works perfectly in XL2000
Any ideas