Search options (Page 128 of 246)

@cambell: Your commit is quite nice. You might want to restrict the use of the TB_PREF to the FROM table alone and not in the other parts of the select statement. The WHERE clause can check for on or before instead of just before date.

$sql = "SELECT supp_trans.trans_no,
       supp_trans.type,
       supp_trans.supplier_id,
       supp_trans.tran_date,
       supp_trans.ov_amount,
       bank_trans.ref AS bank_ref,
       bank_trans.amount AS bank_amount,
       bank_accounts.id AS bank_id,
       bank_accounts.bank_name,
       bank_accounts.bank_account_name,
       bank_accounts.bank_curr_code 
FROM " . TB_PREF . "supp_trans supp_trans INNER JOIN 
     " . TB_PREF . "bank_trans bank_trans ON (supp_trans.trans_no = bank_trans.trans_no 
                                   AND supp_trans.type=bank_trans.type) INNER JOIN 
     " . TB_PREF . "bank_accounts bank_accounts ON (bank_trans.bank_act = bank_accounts.id)
WHERE supp_trans.supplier_id=" . $supplier_id . "
  AND supp_trans.tran_date <= '" . $date . "' 
  AND supp_trans.type=" . ST_SUPPAYMENT . " 
ORDER BY supp_trans.tran_date DESC 
LIMIT 1";

@joe: Want to pull it in?

Fixed in my repo.

Direct Invoice should create a Sales Order and on Delivery, the Invoicing occurs. Hence payment is a separate entry for such tracking.

Sell Cylinder at say $10 per piece and credit-back as and when returned. If there is no price, tracking is difficult in the db.

Try this. The table alias names' prefixes have been removed.

You can store one company per DB or many companies in a single DB with prefixes - prefixes are recommended for security and inadvertant overwriting on wrong company restoration.

The InnoDB engine will need to be large enough to accomodate all the InnoDB tables in all the DBs of the server unless the InnoDB per-table settings are configured. Filesize per file on the OS should also be considered (32 bit limitations, etc).

The size of the data will vary with each company's transaction volume and document attachments.

Servers with upto 10 companies (_0 to _9 prefixes) with transaction volumes to fit into a virtual instance of say 10 GB with 2 fiscal years in open state with 3 users each and not much document attachments can be a ball park figure. The total number of active simultaneous users will be important too as will be bandwidth available and latency, CPUs / speed, RAM and other hardware considerations.

PlaNetTel supported FrontAccounting OpenVZ containers on Debian Squeeze (yes it's old) with 8GB VDisk / 1GB RAM, comes pre-installed with 10 company databases for use with any prefix in each to enable restoration from any other install / prefix.

Please remove the field 0_bank_trans.bank_trans_type_id and state what FA version you are deploying it for.

Also, there are 2 entries for Algemene debiteur in 0_crm_persons table. This affects data in the 0_cust_branch table as well.

Correct the schema of the table 0_cust_branch comparing it with the sql/en_US-new.sql file. Likewise, 0_debtors_master, 0_stock_category and 0_suppliers for field order.

Synch the indexes and their order in the schema of 0_debtor_trans with that in sql/en_US-new.sql so that upgrades will proceed smoothly.

Likewise, synch the field definition of 0_debtor_trans_details.src_id.

The 3rd entry in your 0_item_units table is blank.

Attached SQL file has the tables ordered to match the sql/en_US-new.sql file.

Assuming you have not customised your FA and do not have any extensions installed (other than language)
1. Take a backup opf your sql and web files in FA 2.3.22
2. Upgrade from v2.3.22 to v2.3.25+ (Git Master), upgrade any language extensions if used.
3. Run any incremental sql patches (php) in the sql folder
4. Check your config.php file with the config.default file for any new variables and include them with sane values.
5. Adjust your CoA schema (apart from the collation) to the schema in sql/en_US-new.sql
6. Make sure that your FA is working properly and take a backup (sql and web files)
7a. If you wish to stay within the ambit of the FA 2.3.x series, then install the Fixed Assets extension
7b. Otherwise, you can upgrade to FA 2.4RC1
8. Revert any Depreciation for the current year back to the asset ledger folios using Journal Vouchers.
9. Enter last balance sheet's value into the Fixed Asset register with the depreciation amounts.

Provide feedback to the forum which ever way you chose.

Please note that the FA 2.3.x Fixed Assets Extension needs some extra db privileges - possibly functions, procedures, triggers.

Keeping the Branch Column and adding the Ship_From field along with the appropriate report and sql filters / where constructs and the headings ($cols) will mitigate the Branch filter issue.

1. Create a local Git repo using TortoiseGIT in your windows environment (works with Linux and Mac too) with the core files in a core folder.
2. Place your files in a mods sibling folder. Import the affected core files as is into the same path under your mods folder and commit the change.
3. Make changes to the files in the mods folder and commit the change with information regarding the feature / change envisaged with it.
4. Whenever the core file changes, compare with your modded file and implement the changes thereof in it.

On a Macintosh, the Alt key is called the Option key. It is not used to enter numeric character codes. Instead, keyboard letters and numbers are used.

https://en.wikipedia.org/wiki/Alt_key