From: Bob Phillips on
Hi Neal,

Which email do you have for me (please obfuscate it, don't publish it so
that it can be sniffed out)?

--

HTH

Bob

"Neal Zimm" <nealzimm(a)yahoo.com> wrote in message
news:4031C61C-2D7B-484D-8333-7F2EB24F4B12(a)microsoft.com...
> Hi Bob, Thanks for the post.
> We emailed each other some time ago, I'm the guy who's working on a
> newspaper App. (Still working on it, had to take some time off to earn
> some
> money) and I've not forgotten about you.
>
> You gave me your email address. What's the best to contact you if your
> email has changed? thanks. (It was about a year ago ?)
> --
> Neal Z
>
>
> "Bob Phillips" wrote:
>
>> I maintain a stack array too, I am glad to see that I am not the only
>> oddball. I even call my routines PushProcedureStack and PopProcedureStack
>> :)
>>
>> Bob
>>
>> "Charles Williams" <Charles(a)DecisionModels.com> wrote in message
>> news:8spep5p2cha4ap1omb045lmuspja1o8s13(a)4ax.com...
>> > There is no way of accessing the call stack from VBA.
>> >
>> > For widely distributed addins I maintain my own global VBA stack array
>> > by adding the name of the function/sub into an array at the start and
>> > subtracting it at the end. Then the error handling can display where
>> > the error has occurred.
>> > I also use line numbers and ERL to display the line the error occurred
>> > on.
>> >
>> > regards
>> > Charles
>> >
>> >>When browsing the Locals Window, I happened upon the call stack
>> >>display.
>> >>
>> >>I looked in Help but could not find a way to access it with VBA.
>> >>It might be handy in error processing in knowing how you got somewhere.
>> >>
>> >>If it's available, how do you access it?
>> >>Thanks.
>>
>>
>> .
>>