If you are interested in applications please visit www.VBASolutions.ca .

If you are interested in end-user macros please visit www.TorontoMacros.com .

First: From the end-user’s point of view, List Numbering is broken. I mean that. I’ve always had problems, not of my own making, with list numbering, both in preparing my own course material, and in trying to resolve end-user issues. List Numbering doesn’t work the way any of us end-users think it might or ought. That means that it is counter-intuitive, or it is just plain not-written-correctly in the first place.

I will take you to web pages which document this, to re-assure you that your problems are not really of your own making.

Second: from the VBA developer point of view, any application code that I write will be faced with an end-user system which, most likely, has its List Numbering corrupted by virtue of its being in use.

I will show you how to flush, purge and destroy evidence of any previous incarnation.

Third: We need VBA mechanisms (from which we can provide end-users with an interface that WORKS!) that are fail-safe, and do exactly what we say they will do. The end-user can then decide whether to use our interface (does what it says) or Microsoft’s interface.

Fourth: I typed this numbering system (“First”, “Second” etc) in by hand. I did not use Microsoft Word’s List Numbering system.

Fifth: My back-of-the-envelope calculations shows that if the world had diverted the man-hours involved in trying to cope with Microsoft Word's List Gallery debacle to something that would advance mankind, we probably could have put another man on the moon.

Preferably Bill Gates.

Reading List