Is there something wrong in Line 34 of includes/systypes.inc ?
$sql = "SELECT max(last_no) last_no FROM ($sql1 UNION $sql2) a";
Should it not be (inserted AS):
$sql = "SELECT max(last_no) AS last_no FROM ($sql1 UNION $sql2) a";
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
Is there something wrong in Line 34 of includes/systypes.inc ?
$sql = "SELECT max(last_no) last_no FROM ($sql1 UNION $sql2) a";
Should it not be (inserted AS):
$sql = "SELECT max(last_no) AS last_no FROM ($sql1 UNION $sql2) a";
Line 164 of includes/db/manufacturing_db.inc refers to the X_stock_master.mb_flag - char(1) field with a value of 'A'.
The file includes/manufacturing.inc refers to mb_flag values M, B and D only.
How and where does this affect FA and if so which do we fix?
If and when this is fixed, must it be made out with a flag in the config.php to suit each users need or is MarkAndrews requirement universal - accountants please....
How can you create an item on 5th Sep 2014 (later date) and then expect to purchase it on 31st Aug 2014 (prior date)?
The line 67 in the new includes/db/items_trans_db.inc :
change_stock_moves_std_cost($stock_id, $date_, $new_cost - $last_cost)
is wrong since the difference in cost should be calculated by taking the weighted value of the old cost based on its prior stock value and not merely the difference in cost between previous average cost and current cost as is done above.
The correct calculation should be:
QOH = ( PrevQOH + PurchaseQty ) ;
Avg Cost = ( (PrevAvgCost * PrevQOH) + (PurchaseQty * PurchasePrice) ) / QOH ;
Only mysql_pdo is now fully usable in FA.
If PHP is compiled with large file support then gzopen() (and other such functions I suppose) will become gzopen64() and others like it.
/usr/bin/php -r 'var_dump(function_exists("gzopen"));'
/usr/bin/php -r 'var_dump(function_exists("gzopen64"));'
gzopen() is not found in any of the extensions
It is however found in the following 4 files (line numbers):
admin/backups.php (102)
admin/db/maintenance.php (721)
includes/archive.php (441, 462)
includes/packages.inc (165, 220)
The last 3 files reference gzclose() and gzwrite() as well that may need to wrap gzclose64() and gzwrite64() respectively as well.
There seems to be no reference to gzread in FA.
It is hence prudent to encapsulate gzopen() as gzopen64() if it doesn't exist in the compilation using a wrapper function.
See Forum Posts
Remove Tabs
Remove Hidden menu Items
Please post new subjects as separate posts.
The Official Git repo is now online and is a mirror of the Primary HG Repo.
All of this is stated clearly in my Unofficial Git repo's README.md file and in the FA Wiki as well.
Clever Accounting's Cloud Accounting System is based on FrontAccounting. Anyone used it and if so what is different?
Then Inventory Valuation Report must be right as on the day of preparing the report only. Like Joe stated, "The item cost price can be manually adjusted in the Items and Inventory tab" temporarily for a different past dated report!
Is such a manual now available? This is the only one so far.
Are there any more such constructs in FA now (function is now at line 1613)? In such cases, do the referred corresponding fields in the tables within those in the parantheses get automagically equated?
In this case, the WHERE clause states:
chart.account_code=acc.account_code
should it be
chart.account_code=acc.account_code AND chart.account_code=type.account_code
instead?
Refer the FA Wiki page on Quick Entries and specifically an example of expenses screenshot.
I did not take it from the official git with fetch. I took each release and created my github repo. In recent times I manually extract the files from the official git / hg repo (which ever is current) and then test them in batches when I have the time and then merge it into my repo manually. This method was initially chosen to help in migrating from one version to another. I had published the widely used OpenVZ template publicly till v2.2.11 and many users needed to migrate to the current version.
Changes are generally few and far between except when a release happens.
There may be one or more private extension repos where only "encapsulated" code gets into the FA deployment - a conscious decision on the part of the devs. This way they have control of the community and the code and possibly helps support the development and makes sure the community does not get sidetracked / splintered / misguided.
Furthermore, the devs recommend that all contributions go to their designated email address and not into this forum. This may have something to do with legalese and/or premium deliverables in support of the project.
The end result is that we get to have cool working code well preserved and developed over several years - can't complain at all!
My github repo was made so as to enable the community to
develop extensions on their own and
fix / enhance existing ones and
also to have their own locally hosted extension repos.
In Items and Inventory -> Items the primary database entries (assuming company #2) are:
insert into `2_item_codes`(`id`,`item_code`,`stock_id`,`description`,`category_id`,`quantity`,`is_foreign`,`inactive`)
values
(1,'TUNEV1','TUNEV1','A Tune a Day for Violin - Book 1',1,1,0,0);
insert into `2_loc_stock`(`loc_code`,`stock_id`,`reorder_level`)
values
('DEF','TUNEV1',0);
insert into `2_stock_master`(`stock_id`,`category_id`,`tax_type_id`,`description`,`long_description`,`units`,`mb_flag`,`sales_account`,`cogs_account`,`inventory_account`,`adjustment_account`,`assembly_account`,`dimension_id`,`dimension2_id`,`actual_cost`,`last_cost`,`material_cost`,`labour_cost`,`overhead_cost`,`inactive`,`no_sale`,`editable`)
values
('TUNEV1',1,2,'A Tune a Day for Violin - Book 1','A Tune a Day for Violin - Book 1 by C. Paul Herfurth packed full of lessons, illustrations, fingering charts, daily practice records, test questions, and manuscript paper for homework.','each','B','4010','5010','1510','5040','1530',0,0,0,0,0,0,0,0,0,0);
When the sales price gets entered:
insert into `2_prices`(`id`,`stock_id`,`sales_type_id`,`curr_abrev`,`price`)
values
(1,'TUNEV1',1,'SGD',12);
For your followup question please refer Sales Kits in the FA Wiki.
All of the first 3 need to be setup in your FA instance to achieve what you want. Set up a No Tax entry in the taxes. There is also a stock location transfer method that can be used to avoid any vendor transfer transactions.
Company A defines their inventory stock items and Sales Kits composition of such items
Company A transfers individual component stocks to their storage location in Company B
Company B levies labour charge on Company A (accounted for as a vendor bill in Company A 's accounts)
Simultaneously, Company A now takes back the finished goods from their storage location in Company B back into Company A's main location, but this time it is in units of Sales Kits (components that make a single billable item).
Company A now sells the "Sales Kits" bunched component items set to their customers.
How to do all of this is well documented in the FA Wiki.
A related situation using Manufacturing / Assembling is this forum post.
The HG Repo is quite current with a commit made less than a day ago. It is also mirrorred faithfully on the Official Git but my unofficial github repo will lag a while behind as I update it only after vetting the changes and and when I have the time to do it.
Choosing GitHub over SF's Git repo is a matter of choice:
ease in mirrorring within SF and
the dev's comfort level besides
they may as a policy not like unbridled GitHub forking that may cause identity crisis and
splitting of the userbase.
In Items and Inventory -> Items there is no place to enter the open stock of the Item and the item_code = stock_id and the hardcoded quantity = 1 whilst is_foreign = 0.
In Items and Inventory -> Foreign Item Codes there is a place to enter stock and the item_code can be blank or be set to the ISBN13 code (or EAN/UPC) whilst the stock_id can be non unique since the primary key is the id field and the is_foreign = 1.
Both these entries get into the same table #_items and are treated individually and both forms have the category field - so the same stock_id can belong to 2 different categories if they come from different forms above.
Wiki-ed it.
Use escape character "\"
The Reports page on the FA Wiki is now updated with 33 balance Screenshots - hope this helps potential FA users quickly decide to jump off the fence and into the FA lap.
There is a limitation of the JavaScript-based PDF Viewer in FireFox which currently does not support all the features of the Adobe plugin (or stand-alone version of Adobe Reader). You can test that theory using the steps in this article: How to disable the built-in PDF viewer and use another viewer.
While an end user can switch around among viewers by changing their Firefox options, unfortunately there currently is no way for websites to detect which viewer is in use and assist visitors in a personalized manner. I think for now you may need to recommend that Firefox users use the above article for assistance if more complex PDFs do not render as expected.
You can set the pdfjs.disabled pref to true on the about:config page to disable the build-in PDF viewer.
You can check the value of the plugin.disable_full_page_plugin_for_types pref on the about:config page and remove the application/pdf part if present or reset the pref to the default via the right-click context menu.
http://kb.mozillazine.org/about:config
See also:
https://support.mozilla.org/kb/view-pdf-files-firefox-without-downloading-them
Hope the recent sync of v2.3.21 to v2.4 unstable does this.
The Official Git Repo is now uptodate with the Mercurial one. Thanks.
Import Inventory Items is an extension for FA. It can be installed and activated from within FA. The pertinent files are available for analysis / forking at my unofficial GitHub repo. The format of the import CSV would be the same as the export one and can be culled from the extension.
The Support page on the FA Wiki has a few companies that might be interested in assisting you. Some will even provide you virtualised hosting as well.
The image is quite blurred. The letter head (Header of the Invoice) already has the supplier name and details - putting it above the client details seems redundant.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.