Skip to forum content
FrontAccounting forum
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 124 of 246)
Topics by apmuthu User defined search
Posts found: 3,076 to 3,100 of 6,149
Thanks to @tuananh88c25, Vietnamese Install language files are now committed in my unofficial GitHub Repo and are available at:
https://github.com/apmuthu/frontaccounting/tree/master/FAMods/install/lang/vi_VN
Transifex now has Vietnamese added for FrontAccounting v2.3.x with 1% of the strings translated for now and @tuananh88c25 has been added as a translator at:
https://www.transifex.com/gnuacademy/frontaccounting-1/language/vi_VN/
The Vietnamese core translation files are available at:
https://github.com/apmuthu/frontaccounting/tree/master/extensions/Languages/vi_VN
These files can now be added to the official translation as a pkg file.
Approximtely 250 downloads a week for FA 2.3.25 on SourceForge still.
FA is becoming most popular in Germany in the last year and a half - home of SAP!
Replace line 201 in the new file:
$sql .= " ORDER BY name";
with
$sql .= " GROUP BY debtors_master.debtor_no ORDER BY name";
The said error occurs because you have the same salesman in 2 or more branches and the debtors_master does not specify a particular branch since it should be taken from the transaction itself....
This "licence" to mess up is actually a "feature" to make adjustments that might otherwise mess up standard reports by popping up there.
Anyway, you are right about trackable transactions need to be posted from their respective modules. Thanks for both your workarounds that will surely help others should they traverse the path you did. FA's open database structure saved the day even if taking it's pound of flesh in time and effort.
Upgrade 2.3.12 to 2.3.25+ first.
Then upgrade to FA 2.4RC1.
Otherwise close current accounting year in 2.3.12 and start the next accounting year in 2.4RC1.
Issues like what extensions are installed and need migration / updation, etc will need to be addressed.
This is apart from local customisation / extra fields and external linkages that need to be dealt with as well.
Enable / Activate the Fixed Assets Configuration permissions for your user role (System Administrator) for your company and make sure you have edit rights when you want to make such critical changes as it is disabled by default.
fixed_assets/includes/fa_classes_db.inc defines the function update_fixed_asset_class() which operates on the fields of the stock_fa_class table whose inactive field is not used for now in this file.
Compare the schemas and see if there are any other changes.
Is there any upgrade sql in the "sql" folder that drops the auto_increment attribute?
The only PHP file that refers to the AUTO_INCREMENT attribute is admin/db/maintenance_db.inc in both versions.
Whilst "inactive' is not needed unless it's default / NULL property has changed, the primary key is needed if the AUTO_INCREMENT is absent.
PM access info to check on other system.
Logout, clear your browser cache, login again and then see if you get the same error. You may have used the browser's back button instead of the "back" link on the web page.
It is also possible that your sys_types table may be corrupted or inconsistent. The next_reference field is your target to investigate. This is generally used for transactions and may not apply to new customer creation.
The function add_customer() is defined in sales/includes/db/customers_db.inc - check out the sql in it and manually execute it in some mysql client and see what gives.
Make a new folder for FA 2.4 with it's files.
Copy over the company files for the working companies.
Copy any extensions for the FA 2.4 that were already there in FA 2.3.
The installed_extensions (and the one in the company folder), lang/installed_languages.inc, reporting/fonts must all be copied over from the FA 2.3 with any specifics of FA 2.4 to be inculcated.
Update / create the config.php and config_db.php files in FA 2.4 after referring FA 2.3.
Then when you startup the FA 2.4, your db should get upgraded or manually do so under Setup -> Software Upgrade. Make sure your db was updated to the latest FA 2.3.x before attempting the upgrade. This is necessary for each db / company you have in the installation.
Alternatively, install FA 2.4 afresh and manually create each company and logout.
Manually upload your backup (preferably outside of FA) for each company after adjusting the table prefixes and db names in the sql dump before doing so.
Login to (each) company and do a Setup -> Software Upgrade.
Install your extensions and you should be good to go.
Try:
<pre>
Account number Account name Total amount
311 Bank receivables 300
3111 Bank receivables from HSBC 300
31111 Bank receivables from HSBC HCM city 100
31112 Bank receivables from HSBC Hanoi 200
</pre>
What does it show?
Checkout the setting for $accounts_alpha in config.php file.
Which browser and version are you using now and have you set up the popups appropriately?
Check your spam folder.
Whitelist:
frontacc@sh121.surpasshosting.com
frontacc@gmail.com
Non backport issues
1. Different decimal places for amounts and prices
2. Make all Charts have the tables and fields in the same order and whitespacing, same comment lines - for ease of comparision. Example: UK CoA fixes.
3. Updation of language templates (please add Tamil).
4. Salesman wise reporting
5. Addition of Currency Filter Reports for reconciliation
6. Cambell's$SysPrefs not defined fix. - Fixed.
7.
Possible backport issues (@joe: will not fix as not an issue):
1. Bank Reconciliation and Reporting anomalies
2. Account Groups in Reporting balances
3.
Check out the array variable $aligns in each repXXX.php file.
This was probably left as is due to the fact that some adjustment entries should not show up amongst the actual bank statement entries and confound the user.
@joe: what's your take? Will the proposed solution (exception thrown out) affect the situation more than it seeks to set right?
Allow popups in your browser options. Some browsers have a setting to open popups in new tabs.
Take a look at the 6 digit French CoA (having mixed 2,3,4 and 5 digit chart_types.id) and the mixed 3,4 and 5 digit Spanish ISO CoA.
What happens if $failed_item is either false or NULL / not set in some versions of browser / server php?
Creating Quick Entry templates is entirely in the realm of the user assuming they know what they are doing. Whether any account therein is a bank account or otherwise is immaterial to a double entry accounting system - it will balance, but the bank accounts may not reconcile with bank statement from the bank if you willed it otherwise.
reporting/includes/doctext.inc has the flag to enable preparer display.
reporting/includes/header2.inc displays either the preparer if present, otherwise, the user_id.
The commit link clearly shows the changes.
FA 2.3.x and FA 2.4.x provide for reports in Excel directly and no need for any export. These Excel sheets are readable in all versions of Excel so far. Check your browser settings for mime type associations.
In a fresh blank FA install:
1. Take backup 1
2. Add a supplier.
3. Take backup 2.
4. Backup 1 & 2 diff will provide sql for supplier addition.
Do likewise for
1. adding 1 item supplied by them
2. Adding a price for it
3. Adding a POO that buys it.
Make sure everything works as desired.
Now compare with your currently entered 500+ data and POs and see what needs to be done to match them.
http://climbershaun.blogspot.in/2011/10/handling-upfront-payments-with.html
Posts found: 3,076 to 3,100 of 6,149
