OT? Passive Laddered Accounts: Table Structure?

[PeteCresswell]

Muni bonds.

Accounts within accounts.... sort of.

Somebody buys 150 mil of XYZ into account A

Trade ticket for 150 mil goes to fund accounting and we need to know
that's where the money is.

BUT: at the time of the trade, the trader allocates 50 mil of 150 to
account D as XYZ, 75 mil to account F as XYZ, and 25 mil to account M
- also as XYZ.

Now XYZ's 150 mil is in the DB twice: a lump in account A and three
pieces in accounts D, F, and M.

But we need to report on accounts A, D, F, and M the same way. i.e.
they are co-equals for reporting purposes.

Doesn't seem like a parent-child relationship.

But what is it?

Some sort of recursive relationship?

I've *really* got to get this one right.

Anybody been here?

 

[Tony Toews [MVP]]

But we need to report on accounts A, D, F, and M the same way. i.e.
they are co-equals for reporting purposes.

The exact same reports?

Doesn't seem like a parent-child relationship.

But what is it?

Some sort of recursive relationship?

Yes and if the autonumber key pointing back to the same table is non
null then you know it's a child. This would be identical in concept
to the bill of materials problem. Where a part can be an assembly of
several or many other parts.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/