Search options (Page 187 of 247)

You may also partake of info in the CoA differences post.

My FAMods are critical for me especially the db schema and the added indices and standardised field types and sizes and defaults.

Use a program like WinMerge to study differences between files and files in folders.

Use Excel (or any spreadsheet) to generate your SQL update / insert statements and then use a MySQL client like SQLyog to execute them.

Nice to see someone put their nose to the grind. Someday all of this will be useful to you in guiding newbies get on the FA bandwagon.

The core in my GitHub Repo is a verbatim copy of the stable snapshot (sometimes it is a tad delayed while I take my time to vet each change). You can fork the repo on GitHub whilst submitting patches back as well.

The files in the FAMods folder are to be used to over write their counterparts in the core. Take care when using those in the company folder and only do so if it satisfies your needs - some files will need to be used along with others whilst some others may be used alone. I use all of them. If you use all the FAMods files to overwrite the core ones, make sure you place the shcmds.sh (perms 4755, owner root or equivalent) above your webroot. It is used for some extra functionality in the Setup => Backup and Restore page.

The files in the extensions folder in the GitHub repo are to be used to overwrite their counterparts after installing from the official pkg repo. They are changes that have yet to make it to the official repo open to the public ($ read consultancy $).

1. Overwrite your scriptaculous install with the latest stable snapshot and what mods you desire after taking in the credentials from the config.php and config_db.php files
2. Keep the default company installed with en_US-new.sql and let the default prefix be 0_.
3. Go thru the web install (newer config.php variables will also get in) with the credentials from the earlier config_db.php and config.php files.
4. Login as default company admin.
5. Install the en_CA Chart of Accounts and download and edit the sql file for Canada updating it with the end result of the changes done in the stable snapshot (and recommended from my GitHub repo only if wished and understood) hitherto and upload it.
6. Create a new company with the modified Canadian CoA
7. Logout of the default company
8. Login to the newly created Canadian CoA company.
9. Take a backup of the install and preserve for initial state.
10. Make changes in the Setup menu items to suit your specific install.
11. log out of the Canadian Company.
12. All Canadian company nfo are now in your company/1/ folder
13. Purge the js cache in the Canadian company (rm company/1/js/*.js)
14. Login to the Canadian Company and work along....

The standard Canadian Chart of Accounts too suffers from the field order issue. Check the position of the 0_cust_branch.branch_ref and 0_debtors_master.debtor_ref fields in the sql/en_US-new.sql and yours.

Do not wait for v2.4 - it's been in the making for years now.

Just make the corrections to the tables for benefitting from speed and removing redundant indices and standardising field types and order of fields. There is just too much testing to be done in v2.4 before it can be relied upon - besides, it's schema will keep changing for a while.

All my fixes to the schema in v2.3 are now in my GitHub Repo.

Stating the country you are in (work with) in your profile, will help newbies contact you.

lv_LV is the code to use for Latvian and you can generate your your own lang files from empty.po file.

ru_RU is the code for Russian and is already available in UTF-8 in the official pkg repo to install from inside FrontAccounting.

Default English used is in POSIX "C" language and is latin1 that is iso-8859-1 (it was possibly earlier in UTF-8)

msgid ""
msgstr ""
"Project-Id-Version: FrontAccounting\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2009-11-30 17:03+0100\n"
"PO-Revision-Date: 2009-11-30 17:04+0100\n"
"Last-Translator: Translation Team <info@frontaccounting.net>\n"
"Language-Team: Translators <info@frontaccounting.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=iso-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: English\n"
"X-Poedit-Country: UNITED STATES\n"
"X-Poedit-SourceCharset: iso-8859-1\n"
"X-Poedit-Basepath: c:/Apache2/htdocs/account22\n"
"X-Poedit-KeywordsList: _\n"
"X-Poedit-SearchPath-0: c:/Apache2/htdocs/account22\n"

msgid "Our VAT No."
msgstr "Our Tax Id."

msgid "TOTAL DELIVERY INCL. VAT"
msgstr "TOTAL DELIVERY INCL. TAX"

msgid "TOTAL ORDER EX VAT"
msgstr "TOTAL ORDER EX TAX"

msgid "TOTAL PO EX VAT"
msgstr "TOTAL PO EX TAX"

msgid "Your VAT no."
msgstr "Your Tax Id."

Yes it contains only 5 string translations and qualifies for a language addition in FA!

en_US English in the official pkg repo is also in iso-8859-1

I have made the po and the mo files for the UTF-8 equivalents for en_US and placed it in my GitHub Repo.

You can take the file at  FAMods/lang/en_US-UTF8/LC_MESSAGES/en_US-UTF8.mo, renaming it as en_US.mo and use it to overwrite the one in your FA installation at lang/en_US/LC_MESSAGES/en_US.mo.

You need to make the encoding change in your lang/installed_languages.inc file as well.

It is best to post each issue in a separate post.

FrontAccounting should generally work out of the box and if you want to support the project, then you can use the slightly older but more stable version hosted by the project devs for a small fee at http://my.frontaccounting.com . Unless you state what you are familiar with - computerese, academic accounting, shopfloor experience, banking, manual tax preparation, etc, you will find it difficult to find the right consultant. It boils down to what you want to accept online and what you wish to "possess" and what you want to offload to third parties - in short what is the level of trust you wish to delegate and whether you intend to work on making up your current lack of specific skills to take on the mantle of full responsibility sometime.

Once you have your Chart of Account setup (there is an AU CoA within FA and you can modify it with the help of your local CPA), you can fill in the Setup tab menu's various forms like Company Setup, etc after you create a new company for your business. Keep the default company (Company 0) as your control company and for all working purposes use a newly created one.

Then setup your customers, suppliers, items and manufacturing assembly kits. Import your last balance sheet (and inventory stock) values as a single journal voucher into the last day of the previous year and then close that year and start on your new active current year.

Several links in the wiki point to tutorials about accounting in general and FrontAccounting operations in particular. If there are any specifics you are unable to fathom, we can try to address it by explaining it better in the wiki. That way newbies in the future too can benefit from it.

Please search for any FA support group in your locality (where in AU?) and if you still cannot find one who is cost effective then checkout the nearest one in the support page in the wiki.

Thanks Janusz. That was fast!

Commit Link.