Comments on: New Project Workbook

By: Michael

Michael — Sun, 01 Feb 2009 16:44:00 +0000

Jan Karel -

Could we impose to ask you to share your IsIn function over in the Euler Problem 23 thread I just started? I used an approach I found on StackOverFlow, and would appreciate seeing another way.

...best, mrt

By: sam

sam — Sat, 31 Jan 2009 07:00:00 +0000

Like everyone else… the new project book builds up with time.
some of the most commonly used modules
a) A Control Sheet – with buttons linking to other sheets
c) A Parameter Sheet – where the user selects paths to databases – A Browse for File Module Tied
d) The Kick_butt_find Func – Thanks to Aron T Blood -xl-logic
e) A real LastRow Function
f) A Constants Module – For Application Headers, Stardard Messages etc
g) Help Sheet – Tied to a UserForm – Thanks to J.Walk
h) Sheets with Code names Sheet01, Sheet02 etc so that they line up nicely

I stopped using Menus / Toolbars – for user inputs – 2007 is a sad eventuality….some day and 2009 looks no different

By: Nick Burns

Nick Burns — Fri, 30 Jan 2009 15:23:00 +0000

I've done the same thing for years here at work. I call my "new project" BaseMacro.
Like you said, it's easier to delete stuff, than to add.
I also make use of the document properties to use for the application name, manager names, version and install dates. Very handy.
My projects usually entails using a 3rd party program called Monarch, so I have modules and forms that deal with setting folders up for input files, models, and output.
Modules for menus and command bars.
A library module that contains several general routines that almost every project uses.
Sever different user forms, depending on the type of input needed (some projects may require several files, others just one). I just delete the forms that are irrelevant.
I try to make my projects not look like Excel at all, so there tends to be several hidden sheets that many contain user defined data that can only be accessed via menus. Also just a main screen with the company logo and title of the project. If the title says Base Macro, I know that I haven't set the document properties up yet. This gives all the macros for the company a standard look and feel.

I do have the Professional Excel Development book, just haven't had the time to peruse it in depth yet. I've always wanted to set up a general error handler. I have a simple one made up, it just doesn't have a very polished look to it.

By: Ross

Ross — Fri, 30 Jan 2009 12:33:00 +0000

I don’t have a project, but I have some modules & classes that have sets of functionality, I just drag them across as i need them, it’s not like they add much to the workbook size, so even if i want just one thing from a modual, i will put the whole lote there – lazy, but easy! I also try t get the standard modules to work like classes – i.e. replace able in any project, but it never works! Mainly because I go ” oh well i go do this properly, but just for this project I do it like this”!

By: Jan Karel Pieterse

Jan Karel Pieterse — Fri, 30 Jan 2009 10:45:00 +0000

I tend to include an modFunctions for generic functions like fUsedRange (which finds the true used range based on cell content), IsIn (which tells you if an items belongs to a collection) and things like that.
And then I have modUtilities, which contains all sorts of small routines to do things like tidying up of styles, listing styles, checking template integrity regarding range names and lots of other stuff. This module only gets included on files where I do heavy lifting Excel work as opposed to plain vanilla VBA programming: e.g. when I build reporting templates.

By: AlexJ

AlexJ — Fri, 30 Jan 2009 03:27:00 +0000

Dick,
I've just started building a similar construct called AppCore - just like it sounds, it is what all my other apps are built around. As well as similar stuff to your examples, I'm including standard security and access stuff, standardized interfaces to databases, standard logging, version and release control, debug tools, etc.

Biggest challenge is retrofitting changes to AppCore "2.0? into AppCore "1.0?. I haven't constructed AppCore as an addin yet, and I'm not really looking forward to it.