The over-zealousness of this post bleed'eth over..... I think you may wish you would have invoked your sysop powers to delete this one.....<s>....

While I think Jim Booth's reply to you said it best... I would like to share a few thoughts....

Emotion is a very formidable tool. When used properly, it can be your best friend. When use improperly, it can be your worst enemy.....

In a GL Tx file, you may be attempting the following JE (the numbers are just made up to illustrate the point:


Payroll Expense 1000
Salaries Payable 700
Medicare Tax Payable 125
SS Tax Payable 200
State Tax 75


In a GL tx system, each of these entries are separate records. They either to commit in their entirety, or none of them should take....

BTW, my undergradutate degree is in Accounting. Prior to finding out that the world of debits and credits was too boring, I passed half the CPA exam, and I was a corporate controller at the age of 28. That is why I switched my MBA major to I/T, from Finance. What you could possibly teach me about accounting would fit in something smaller than a thimble....

That said, since accounting is fairly vanilla, I don't think there is a lot of NEW design work that could be done in accounting systems today. But, I appreciate the shot towards me at the end of your post.

It shows some spunk!!

Next time, don't let emotion be you enemy....


>Hello! Since when do debits and credits commit separately? A transaction in an accounting situation should balance per commit. That is, all credits and debits within the same journal entry must be committed co-equally. Or rolled back commesurately as may be the case.
>
>Remind me not to ask you to design my accounting systems :-)
>
>
>
>>Good examples include accounting-based apps. Both the debit and credit >updates need to be committed. If one does not commit, the other should not...
>>
>>It is a fairly simple concept.......