It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
Make a list of reports in FA where VAT is used that you would like to get rid of and see if a mere translated string can be hardcoded (as possibly blank) or removed from it. All such report files are in reporting/repXXX.php though the header files reporting/includes/*.inc/php.
It is indeed quixotic that the default CoAs distributed with FA are for the US whilst the EU/Asian VAT/GST seems to be in them!
When posting information on an error you should post the choices made in the preceeding form. Assuming you chose the en_US-new.sql Chart of Accounts in the previous form, line 42 in sql/en_US-new.sql is:
`tran_date` date NOT NULL default '0000-00-00',Some recent versions of MySQL do not allow '0000-00-00' as a valid date field value. Try removing all such constructs (default '0000-00-00') from the said sql file and re-try the installation after emptying the db. Alternatively set strict mode off in MySQL.
The following links provide further info:
https://dev.mysql.com/doc/refman/5.6/en/datetime.html
http://stackoverflow.com/questions/25349126/how-can-i-set-the-default-value-of-a-field-as-0000-00-00-000000
http://stackoverflow.com/questions/36374335/error-in-mysql-when-setting-default-value-for-date-or-datetime
The error is because of the sql mode which can be strict mode as per latest MYSQL 5.7 documentation
MySQL Documentation 5.7 says:
Strict mode affects whether the server permits '0000-00-00' as a valid date: If strict mode is not enabled, '0000-00-00' is permitted and inserts produce no warning. If strict mode is enabled, '0000-00-00' is not permitted and inserts produce an error, unless IGNORE is given as well. For INSERT IGNORE and UPDATE IGNORE, '0000-00-00' is permitted and inserts produce a warning.
To Check MYSQL mode
SELECT @@GLOBAL.sql_mode global, @@SESSION.sql_mode session
There are a total of 31 places in the en_US-new.sql file where the said construct is there.
There are many places in the php codebase where the equivalent of the following constructs are available:
if ($date == 0) $date = '0000-00-00';and
$sql .= " tran_date > IF(ctype>0 AND ctype<".CL_INCOME.", '0000-00-00', '$from_date') AND";Hence it is better to turn the strict mode off in the mysql and not tamper with the Charts sql.
All email in FA are sent using the class email which is in reporting/includes/class.mail.inc.
Search for the text "new email" in the FA code and all such places that use it will emerge and in FA it will be:
reporting/includes/inventory_db.inc => function send_reorder_email()
reporting/includes/pdf_report.inc => function FrontReport::End()Since it is inside functions, search recursively for each function call in the codebase.
You mentioned that you are a "experienced Front Accounting..... expert" .....
Kindly note that FA 2.3 is quite mature whilst it's CoAs in the official repo are not all of the "exact" schema. Since you are implementing FA for your clients, you will do well to check out the extensions development in the unofficial repo as well besides the FAMods.
Other than being free what made you choose FA after so much experience with "big ERPs"?
Cheers and good luck. Enjoy FA.
For those trying to install FA 2.4RC1 in the pt_PT and de_DE languages, the corrected language files for the installer are zipped up and attached in this post. The necessary diffs are in my commit that can be pulled into the Official Repo by the devs.
For those using the Charts of Accounts from the Official FA 2.4 PKG Repo, be aware that they have not been updated in a while. As an example, a diff for the en_US-4digit.sql has been done with the standard sql/en_US-new.sql and arranged for easy comparision with the original and attached herein.
It appears that the FA pkg files in the official repo get regenerated together for both FA 2.3 and FA 2.4 changing only their timestamps. There appear to be no changes in over 6 months now in the pkg files in the FA 2.3 official repo as on date. My unofficial pkg repo has the pkgs as farepo.zip.
All that is required is to manually create the taxes for each State in FA and backup the tax tables for import and use by others.
FA is really "Single User" as far as multiple simultaneous submits to a form are done at least in FA 2.3.x. Hence when 2 or more users open a new invoice form, all will have the same "next" reference number in it which tries to be posted and only one succeeds.
Put the phone number in the TaxID field.
Make a copy of the sql/en_US-new.sql or other Chart of Accounts sql file you are using - and name it uniquely and place it in the same sql folder after editing the currency and other details in it.
Edit the file config_db.php and remove the offending entry in the $db_connections array.
State which version of XAMPP / PHP and OS, FA you are using.
In both FA 2.3.x and 2.4.x, the function user_company() is defined in includes/current_user.inc file.
See if any info in this post solves your issue.
Journal Entries.
The file includes/dashboard.inc in FA 2.4 uses several translated strings like "Top $limit .....". Where do these translations reside?
I trust it is a self join with:
0_debtor_trans_details.src_id = 0_debtor_trans_details.idYes. That is what Manufacturing is. If you wish to make it separate Manufacturing orders, split the raw material quantities on separate orders to what is needed for the one manufactured.
CAS (Central Authentication Service) like a Single Sign On is possible with FA. Check the login code and what values accrue in it's session and make sure the CAS replicates it on login.
You can state all pre-deducted charges in the description and use the net price in your invoice.
Check the collation and charset of the old and new dbs.
Also check the PHP / MySQL / Apache versions of both installs.
There may be some missing php modules (php -m) in the new one.
Create an invoice manually in FA for one invoice from Unicenta. Take the diffs of the before and after backups and you will see what has been inserted and what has been updated. Do the same in your procedure directly into FA's tables.
State versions of OS, platform and FA used.
You can use the company number in an if statement to prevent it's inclusion / execution for the specific company you want to suppress it for. The currently logged in company should be in the session.
You may have some dummy entries in the table that links entities (branches) to contacts - FA's basic CRM tables. See the ERD link in the wiki alluded to in the second post in this thread.
https://frontaccounting.com/fawiki/index.php?n=Devel.BarCodeUsage
has the necessary code.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.