Outline codes

  • Thread starter Thread starter Hydra
  • Start date Start date
H

Hydra

I need to create an outline code that ollows the format A.1.a. It would be
useful but not necessary if I use it for the index as well. At present I have
a form that accepts entries and numbers them correctly in the format 1.1.1.

Any suggestions on how I can reformat those numbers for presentation on a
report? This is an app that helps construct an IMP or integrated master
plan, which is a precursor to an IMS which will be created in MS project.
 
I haven't taken on this task before, but I think it may be very close to a
Bill of Materials structure. Have you looked into BOM handling?

For instance, in a BOM structure you might have a table that looks like this:
tblSomethings
fldID
fldParentID
fldOtherInfo

.... and a little bit of query work to handle the data accordingly.

Outlining I think would follow the same lines. Essentially you have a
single item had has an unknown number of children, or nodes if you like that
better.

The next thing I think you would need is some table to dictate what
character to display (uppercase, number, lowercase, roman numeral, etc) for
any given level. Something like:

tblOutlineLevels
fldLevel (1, 2, 3, 4, 5)
fldDesignator(UCRN, UC, N, LC, LCRN)

Assume:
UCRN = Uppercase Roman Numerals
UC = Uppercase Letters
N = Numbers
LC = Lowercase Letters
LCRN = Lowercase Roman Numerals


Then, for any given ID, you can, with your fancy BOM-like query work,
determine the nested level of the item and assign it's character and value
accordingly.


Maybe I'm way off base here... this is just off the top of my head (how I
would go about it before I found a better way). Possibily someone already
has a much better system for handling outlines? You can't be the first to
ask...


just a thought

hth

--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
 
You have outlined thoughts similar to what I had, but I was hoping for more
magic.

A BOM would be similar in structure, but limited to three levels, like
prudct, subbassy, and component. An IMP has only Events, Achievements, and
Criteria. If you can complete all the criteria, you collect credit for an
achievement and when all the ahcivements are met the event is completed. So
to have a program kick off meeting yu need authority to proceed, you need a
management team, and you need a plan. Each of thase have spedcific criteria:
for Authority to Proceed the criteria are you need to win a program and
complete negotiations.

What I have is a database in which you can enter events, achievements, and
criteria. The major events are pretty standard: Kick off, requirements
review, PDR, CDR, etc. A given program might have new or additional
achivements required for an otherwise standard event, and the criteria have
still more latitude.

That database has key fields that are autonumbered. the user just
downselects to his needed major events, then for those downselects the
applicable achievements, and for each of those downselects the necessary
criteria, or maybe add new achivements and criteria.

I really have two problems. The report I have shows the selection in outline
form, but it uses the key fields as the outline code, so you wind up with a
report that is numbered in sequence, but with gaps: 1.1.1 thne 1.3.5, maybe.

I need to renumber the report to 1.1.1, 1.2.1 etc. and then translate THAT
toan Alpha sheme like A.1.a, A.2.a, etc.

This probably means using look up tables, as you suggest, but it would sure
be nice to just have a calculated field. I'd have to count the number of
selection s from the event table and number them A,B, C. then for each of
those I'd have to count the number of entris from the achievement table and
number them 1, 2,3,restartig the numbering at ach Event change, and then
number the criteria as a.b.c. starting over for each new Achievement.

Didn't the German enigma machine work that way, with a bunch of cascading
spinning disks?
 
Sorry, I'm too practical for magic <g>

Being that you already have some recordset returning the ordered records
that you want, I would think you should be able to come up with some scheme
to loop these and increment them accordingly. Of course, you would need some
custom functions to define the identifiers to use based on the nested level.

Fortunately for you, the easy part of it, getting the records in the right
order, is already done. Not that the outlining is a simple task... sorry,
if I had more time I would try to come up with something, but I'm afraid it
might be a while before I can get to.

good luck


--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
 
Back
Top