Implied Option Explicit in XP??

[Trip]

Hello all,

Quick question here. It seems as though XP is enforcing "Option Explicit"
even though I don't issue this command anywhere in my VBA code. The code
runs fine in other versions of Excel, but in XP it hangs anywhere I have not
explicitly defined a variable's type. Does anyone know why and/or what's
going on? Any direction would be greatly appreciated.

Thanks!

Trip

 

[RWN]

In the VB Editor, is the "Tools->Options->Editor" "Require Variable
Declaration" selected?
Don't know if this would be your problem, but it seems related.
--
Regards;
Rob

Please reply to the NG, I'm already up to my eyeballs in Nigerian/South
African get rich letters
as well as "Microsoft Critical Updates" et al.

 

[Jerry W. Lewis]

Look elsewhere for the problem, XP does not default to Option Explicit.

If in the VBA editor you check
Tools|Options|Require Variable Declaration
then Option Explicit will be added to each new module, but it will be
explicitly there, not implicitly required.

Jerry

 

[RWN]

Didn't think so, but it was "worth a shot" (what do I know, I'm far from
an expert!)..
I tried it on XP and had no problem (doesn't help much, I know).

When it "hangs", is it complaining specifically about not being declared
i.e. what does it do/say?
Is it with just one, or any, module?

--
Regards;
Rob

Please reply to the NG, I'm already up to my eyeballs in Nigerian/South
African get rich letters
as well as "Microsoft Critical Updates" et al.