Declaring Dim, Public

In one module in my PERSONAL, I have around 20 different macros for working with pivot tables. In each one I have a "Dim PT as PivotTable", "Dim PF as PivotField", etc. I thought it might better to declare all of these at the top of my module rather than individually in each macro, but I'm confused on the best way to do that.

From what I've read, Dim is more "private", vs Public, which is more "public" (see http://www.vbforums.com/showthread.p...l-Static-Const).
See the examples below. Would it serve me better to have all of the bottom four as PUBLIC, or as DIM?
And how about for any add-ins I build for my users; what's the best way to go there?

Please Login or Register  to view this content.

Jeff,

Thanks so much for clearing up my understanding. One of the things I was trying to do was get consistent in my naming conventions; I have macros that I've created, and some that I've adapted from stuff found online, and some that were responses to questions I posted. So, there's a lot of variation in, for instance, PivotTable; it might be PT, or Pvt, or Piv, or PTab. So my thought was I could replace all of these with PT, and then it seemed that it would be most efficient to declare it all at the top of the module.

My question on Add-Ins was just to find out if there was any different special consideration I needed to give to my add-ins, since I share my home grown add-ins with other users.