Search options (Page 144 of 247)

You can use the company number in an if statement to prevent it's inclusion / execution for the specific company you want to suppress it for. The currently logged in company should be in the session.

https://frontaccounting.com/fawiki/index.php?n=Devel.BarCodeUsage
has the necessary code.

If the petty cash paid and petty cash received have been incorporated into the cash and bank accounts, then they should be zero or at the very least equal to one another with sign reversal. Make a journal voucher moving the amounts in balance in each of the petty cash accounts to the cash account and then use the resultant trial balance.

Alternatively, a credit of maximum usage can be agreed upon and provided as a loan to the customer and advance received back into the customer's account.

A credit limit too can be used.

Check the history of file changes for the said file in github.com and see if an upgrade to the latest FA v2.3.25+ is of any use.

Choose default theme - no dashboards. Dashboard themes do too much querying for each front page display.

Try treating Commission as a pseudo tax using a separate Commission Account that receives it (or pays it out if negative).

Otherwise, make an extension for it.

Difference compared to FA 2.3 would be useful if illustrated.
Attached is your page in PDF.

Check the MySQL and platform versions. Also do a query to take the difference of the field value from a zero constant. It is possible to assign 0 instead of 0.00 in the insert statement in the backup sql and re-import it.

Just re-compile the standard en_US.mo file. Only changed strings need be in the new .po file and compiled into the .mo file.

In the case of Australian or Indian English too the same applies with changed strings.

Extract the .po file from your current .mo file - only those stings that changed need/will be there. Then refer to the empty.po file and add in "the strings you wish to change" into the extracted .po file and recompile and use it.

In future, do not upgrade the language file at all from the GUI and instead only incorporate the changes in them into your version of the extracted .po file, compile and use the resultant .mo file.

In most instances language files have little or no changes and version bumps occur regularly - good business for "consultants".

Do not edit the _('DELIVERY NOTE') as it is a translatable string that needs to be altered in the appropriate .po file which then needs to be compiled into a .mo file before being used.

If you are using only 1 language and/or prefer this string to be in English alone, hard code it using the following instead:

                {
                    $rep->title = 'CUSTOMER INVOICE';
                    $rep->filename = "Delivery" . $myrow['reference'] . ".pdf";
                }

As the db_pager_view.inc is a core file, modifying it may not be good. Checking the file that @joe suggested may be useful.