Pi not defined?

**geoB** · 03-24-2009, 03:03 PM

XL2007, sp1:

In a VBA module doing some trigonometry, I want to use the value of pi. Yet when I compile, Pi is highlighted as "variable not defined", although it is listed as an available worksheet function. Pi(), when compiled, returns sub or function not defined.

And the workaround is...?

[and searching on pi doesn't help. sorry.]

TIA.

George

**Everstrivin** · 03-24-2009, 04:01 PM

You could just dump your formula to a worksheet cell have it calculate, then pull the result back into the code. Just a thought.

**DonkeyOte** · 03-24-2009, 04:08 PM

Perhaps you mean

Please Login or Register  to view this content.

**geoB** · 03-24-2009, 04:44 PM

My eventual solution:

Please Login or Register  to view this content.

, where value was pasted from a cell using =pi().

So it can be used throughout the module.

g

**DonkeyOte** · 03-24-2009, 05:00 PM

That makes sense but to reiterate you can just use Application.Pi, the below

Please Login or Register  to view this content.

is not a valid VBA expression... ie you were trying to use Native XL syntax in VBA which isn't going to work I'm afraid unless encased within an Evaluate call, eg:

Please Login or Register  to view this content.

Or as outlined using VBA syntax, either of:

Please Login or Register  to view this content.

Please Login or Register  to view this content.

Hopefully this will help you as you move forward and use other Native Functions directly from VBE.

**geoB** · 03-24-2009, 05:09 PM

Forgive my ignorance of VBE, but wouldn't

Please Login or Register  to view this content.

be required in each procedure needing pi? By placing a constant in the module declarations I get to use it in all procedures in the module without further ado. Is this method not recommended for some reason?

g

**DonkeyOte** · 03-24-2009, 05:17 PM

If you read my post you'll note I first said:

"That makes sense"

I should perhaps have clarified that this related to using a Public Constant....

I was merely trying to make a point re: your initial post / question and how you can / should handle XL's native worksheet functions when calling from VBA ... plainly I'm failing in my objective so I shall not muddy the waters further
(confirmed by the example you used in your last post... ie the only one I posted that I said wouldn't work!)