>PROCEDURE CalcSomeThings
>PARAMETERS tcEmpCode,tdLastWorkDay
>
> * 1. Setup
> * 1.1 Check if params valid
> ... do checking, take action
> * 1.2 Open tables
> ... open them
> * 1.3 Other pre-verification

Nice, actually I also start some things in form of a outline comment, specially if it's to be done by someone else. Saves me lots of explanation.

I only don't see any point in numbering - the actual order of events may differ in the final version, and once you look at the code with the outline numbers out of order, you just begin to wander what's wrong, when it's actually OK.

BTW, how does one outline a form? What's the rule-of-thumb approach when you want to write the specs for a form? Write down all the objects with just descriptions of behavior, or what?