Search options (Page 129 of 247)

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

You are trying to change the heading label - it has nothing to do with the actual field from where it comes. The type array element is for formatting the column and also has nothing to do with the contents of any table's field.

Anything like: _("string") is shortform for gettext("string") and is changed by changing the *.po file and compiling it as *.mo file using msgfmt. Refer the Translations page in the Wiki.

To achieve what you want, pick out the strings that are affected and then trace the translation strings in the appropriate .po file and edit them in a text editor using "No BOM" format and then compile it it as the *.mo file and replace it in the fa install.

The order of the inserted fields must match the order of the values to be inserted in them.
Your first bold SQL code entry:

        order_type, ship_via, deliver_to, delivery_address, contact_phone, shipper_address, ship_from,

should be:

        order_type, ship_via, deliver_to, delivery_address, shipper_address, ship_from, contact_phone,

Have a common FA instance for the company. Use SimpleInvoices or some Point of Sale software that take care of AR / AP. Synch the FA with the AR/AP application at any desirable frequency.

Please read the whole thread. This is not a standard feature in FA (both versions). Someone posted their screenshots somewhere else and I placed here for self-sufficiency of the forum. You are free to develop an extension for it. Pharma products is one example where batch number and expiry date will be needed for sale and returns.