"Jon A. Christopher" <[EMAIL PROTECTED]> writes: > Eliminating single-entry would be a mistake IMHO. Who wants to learn a > new system of accounting just to balance their checkbook? But my question was, WHAT is it about double-entry that's new? It doesn't change the way you use gnucash AT ALL, except that you are required to have a "category" for every transaction. Are you seriously saying that that's too much for you? > Not me. I'm a programmer and geek, but for some things, I just want > to use the bloody software, not become one with it. I just don't get it. I agree that you might not want to go to the effort to become "at one" with a piece of software, but I can't see how using double entry fills that description. I'd appreciate it if you could explain so I can understand where you are coming from. Bill Gribble
- Re: gnucash 1.3.7 bugs. Rob Walker
- Re: gnucash 1.3.7 bugs. Dave Peticolas
- Re: gnucash 1.3.7 bugs. Jonathan Corbet
- Re: gnucash 1.3.7 bugs. Hendrik Boom
- Titling of Register Columns Christopher Browne
- Re: Titling of Register Columns Dave Peticolas
- Re: Titling of Register Columns Richard Wackerbarth
- Re: Titling of Register Columns W. Scott Wilburn
- Re: gnucash 1.3.7 bugs. Bill Gribble
- Re: gnucash 1.3.7 bugs. Jon A. Christopher
- RE: gnucash 1.3.7 bugs. Bill Gribble
- RE: gnucash 1.3.7 bugs. Rob Coker
- Re: gnucash 1.3.7 bugs. Christopher Browne
- Re: gnucash 1.3.7 bugs. Rob Walker
- Re: gnucash 1.3.7 bugs. Scott Haug
- The Single Entry Approach Christopher Browne
- Re: The Single Entry Approach Rob Walker
- Re: The Single Entry Approach Richard Wackerbarth
- Re: gnucash 1.3.7 bugs. Jon A. Christopher
- Re: gnucash 1.3.7 bugs. Rob Browning
- Re: gnucash 1.3.7 bugs. Christopher Browne
