Geting AfterEffect Information

[Abhishek]

Hi!

I need to know how can i prevent an exception to come in my code. I using a
very simple example.
I am procccessing the animations of a presentation

While extracting the information for AfterEffect
(sEffect.EffectInformation.AfterEffect)
I get exception whenever there is no afterefect given to the animation.
This is obvious that it will give an error if aftereffect does not exists.
Is there a way in which i can determine whether aftereffect exists or not so
that I am not faced with the exception.
I am using PPT 2003


Abhishek

 

[Steve Rindsberg]

Hi!

I need to know how can i prevent an exception to come in my code. I using a
very simple example.
I am procccessing the animations of a presentation

While extracting the information for AfterEffect
(sEffect.EffectInformation.AfterEffect)
I get exception whenever there is no afterefect given to the animation.
This is obvious that it will give an error if aftereffect does not exists.
Is there a way in which i can determine whether aftereffect exists or not so
that I am not faced with the exception.
I am using PPT 2003

Sometimes the only way you can find out something like this in PPT using VBA is
to set an error trap, try it, and if it triggers the error trap, you've learned
what you need to know. I'd imagine there's a similar approach you can use.

 

[Shyam Pillai]

What is the type of shape in question? Which is the animation applied to the
shape?

 

[Abhishek]

Sometimes the only way you can find out something like this in PPT using VBA is
to set an error trap, try it, and if it triggers the error trap, you've learned
what you need to know. I'd imagine there's a similar approach you can use.

Yes I am using a similar approach but i just wanted to know if thereis any
way that i can find out other than the error trapping method because error
trapping slows down the processing considerably.

 

[Steve Rindsberg]

Yes I am using a similar approach but i just wanted to know if thereis any
way that i can find out other than the error trapping method because error
trapping slows down the processing considerably.

That's odd. I've never noticed any major speed hit in VBA, but each language
has its peculiarities I suppose. Still, being unable to write error handling
code w/o slowing down the application badly would be a major drawback, IMO.

You might be able to isolate the error trapping to code that only runs when
you're testing certain types of objects.