First Post of the Series
Previous Post in the Series
Download and install GnuCash from www.gnucash.org. At the time of writing, the latest version is 2.4.11.
GnuCash was originally available only for Linux and other Unix like operating systems. It has been available for windows since release 2.2.0, released on 15-07-07. GnuCash initially used only an XML based database format. Release 2.4.0, released on 21-12-2010 was the first to give the option of using an SQL database (SQLite, MySQL or Postgres) (The versions mentioned are the first stable versions)
It is my perception that the reports run faster if a database backend is used. The other difference is that using an XML backend requires that the file be saved once in a while. The database backend does not require to be saved. After tinkering a while, I found that an XML backend is the only way you can ensure that the data file is portable across OS's- The same file can be opened in GnuCash under Linux without any hassle. (I may be wrong about this, infact I suspect that I am. If so please let me know through the comments box below). I found the GnuCash GUI much slicker under Linux than under Windows.
If you want to use GnuCash for the purpose these blog entries were written - i.e. maintain the books for a church, do not run the new account hierarchy wizard now. My next post will explain how to create a typical account hierarchy suitable for use by churches.
Please enter let me know your comments and suggestions through the comments box below.
Next Post in the Series
Previous Post in the Series
Download and install GnuCash from www.gnucash.org. At the time of writing, the latest version is 2.4.11.
GnuCash was originally available only for Linux and other Unix like operating systems. It has been available for windows since release 2.2.0, released on 15-07-07. GnuCash initially used only an XML based database format. Release 2.4.0, released on 21-12-2010 was the first to give the option of using an SQL database (SQLite, MySQL or Postgres) (The versions mentioned are the first stable versions)
It is my perception that the reports run faster if a database backend is used. The other difference is that using an XML backend requires that the file be saved once in a while. The database backend does not require to be saved. After tinkering a while, I found that an XML backend is the only way you can ensure that the data file is portable across OS's- The same file can be opened in GnuCash under Linux without any hassle. (I may be wrong about this, infact I suspect that I am. If so please let me know through the comments box below). I found the GnuCash GUI much slicker under Linux than under Windows.
If you want to use GnuCash for the purpose these blog entries were written - i.e. maintain the books for a church, do not run the new account hierarchy wizard now. My next post will explain how to create a typical account hierarchy suitable for use by churches.
Please enter let me know your comments and suggestions through the comments box below.
Next Post in the Series
No comments:
Post a Comment