|more useful options|
Thanks for your interest. Life changes have pulled me away from my accounting system work. I am just getting back into it and am grappling with the user interface.
That interface is to be in Tk, but I am trying to keep a separation of concerns.
The working name is Rbks. It is a fairly simple and flexible double entry bookkeeping system. As it stands now I have the General Journal backend code fairly squared away. Which is to say a Gj_entry posts itself correctly.
Ledger and journal reports don't concern me much. These seem to be straight forward SQL reports. I haven't found any strong justification to have reporting be part of the objects. I am open to argument and think the design is flexible enough to add this.
I have looked at the ledgerism reference. For practical purposes I have a distrust of such all encompassing models. The other links you give don't work for me.
I am researching scaffold code for basic database Find/Prev/Next/Add/Update/Delete interface screens. If I don't find anything soon I'll be posting a long SOPW.
I'd rather have an interface before releasing code, but I
am willing to share the overview info.