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 62 of 245)
Topics by apmuthu User defined search
Posts found: 1,526 to 1,550 of 6,111
FA is multi tenant. You can choose to hos each company in a separate database or use different table prefixes and place them in the same table. Each "tenant" is then chosen in the login screen. The FA code is just a single instance but each company has it's own folder for it's data files.
If you create User A in both companies with same / different passwords, FA will accept that as well, since the users table is different for each company (with either different table prefixes in the same database oand/or different databases).
The tree structure actually exists in FA only that it appears flat in a table. With the sub-ledger concept, the parent-child relationship exists but not used by most. Drill Down is also available in FA. You can write a script to read the chart of accounts and display it as a tree for your understanding as an extension if you want.
The following service providers support XCD:
Oanda
mataf.net
CoinMill.com
XE.com
GoodReturns.in
Maybe we should use a plugin system for Exchange rates.
A suggested mod may be in order in the meanwhile.
If you use the sql/en_US-new.sql as your Chart of Accounts it will be without the dummy data.
Then, don't forget to logout and login again.
@joe: should a flag be used or should it simulate the old functionality with the inclusion of the said code?
This is clearly a FA user and company instance. The login system uses the company name from the $db_connections array in config_db.php file. The login user and password come from the appropriate database's users table.
If you need to implement it this way, then the following should suffice as $qoh=0 for the first computation:
if ($qty > 0 && ($qoh != -$qty)) {
if($qoh == 0 && $avg_cost != 0)
$avg_cost = ($avg_cost + ($unit_cost*$qty_new)/$qty)/2;
else
$avg_cost = ($avg_cost*($qoh+$qty_delayed)+$unit_cost*$qty_new)/($qoh+$qty);
}
Hope the first computation too will remain a weighted average cost.
@joe: Please verify and include if okay. Why was this done in the first place - was it the remnant of some debug coding? Or must there be a flag to suppress zero entries?
@joe: is this the desired design outcome?
The last version of CMS archived home page is of v12.1 / 2009. They still state that they are a Microsoft Silver Partner and the DB may still be MS SQL Server.
You may want to use the SlimAPI as a REST client to push batch info into FA.
The version of the REST API tested for FA 2.4.x is here.
Is there any other js / ajax / php check for such duplicates in the Customer Short Name scripts that needs to be put in for the Supplier scripts as well apart from the unique key?
Whilst the Denali version uses the MS SQL server, what database does the legacy version use?
Could not trace the old legacy version to study it.
You can run VMWare Player in your Win7+ workstations and run WinXP in a Virtual Machine in it where your legacy CMS client can run. That way, you will not need to change the software and the way you run your business.
Have you setup your Chart of Accounts in FA and tailored it to suit your existing one in the legacy CMS?
You will need to use the latest FA v2.4.4+ Git Master as it sorts out quite a bit of issues.
Perform one batch of one type of transaction with just one transaction in it and compare the before and after backups of the sql - you can then figure out how to frame the SQL statements to import a full batch.
Can be done purely as SQL statements in order without any user intervention - bash/sql/cron - at specific times.
WHat is the legacy accounting used?
Do the legacy accounting program and FA reside on the same machine?
Committed.
Kindly verify if the functionality is okay.
Looks like a rollback of this commit is in order if no new workaround is found.
Make an extension for it. Hopefully all entries for the customer are in place before the extension triggers these entries.
A Quick Entry based on manual calculation may be in order till then.
This is necessary as the last function in it (function parse_notes_params) is needed in some instances.
See the Wiki.
Try clearing the js and other browser cache and try it.
@kvvaradha: Since you are making a LEFT JOIN for the voided entries, there could be many null voided entries in the result set that would have the v.date_ field as NULL anyway!
@joe: can polish it up and check and include it if needed.
@joe: the whole commit can be reviewed instead of the fixed part alone.
Posts found: 1,526 to 1,550 of 6,111
