Lay it out exactly like that - we do this in several places where the "loose" hierarchy of steps and levels is not exact

Code:
Appl   Job   Schedule   Step   Direction   Flag1   Flag2       Value, etc...
 1      1        1        1        I       Year?   valid=Yr    2008
 1      1        1        1        I       PO?     
 1      1        1        1        O       .file               .\SaveStep.tmp

 1      1        1        2        I       .file               .\SaveStep.tmp
 1      1        1        2        O       .printer            HPDeskJet
You can add extra levels between STEP and DIRECTION to have all kinds of sub-levels and conditional levels.

You are kind of in the realm of 4th, 5th and 6th levels of normalization - where the "memory" and "application" use of the data is much more important then the "storage" of it.

Post 5 and 8 of this thread dives a bit into this

http://www.vbforums.com/showthread.p...56#post3230256