Search options (Page 143 of 246)

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.

If you decide to retain the transactions for Jan-Mar in the old accounting system, then enter the march end closing balances as the April 1st opening balances by making a journal entry for the mid year Balance Sheet and P&L entries (entire Trial Balance) as of 31st March.

In the case of migrating to FA during start of a fiscal year, only the Balance Sheet closing balances of the previous fiscal need be carried forward.

Grown is Manufactured over multiple years just like if the manufacture started in one fiscal year and ended in the next one. In the interim period whilst it is being grown (manufactured) it will be considered "in process". Stock valuation can be based on "accrued value" much like if the exchange rate changed or in semi finished state.

Alternatively, the inputs for "growing" can be considered as stock consumed / applied / expenses or paid in advance to  a dummy supplier. Just before sale of grown items, they can be purchased from the dummy supplier at 0 value or at pro-rata of advanced to dummy supplier and then sold at profit to end customer as usual.

I think you need to change the size of the form field's maxlength value:

<input _last="" name="_code_id_edit" id="_code_id_edit" size="12" maxlength="10" value="" class="combo3" rel="code_id" autocomplete="off" title="" type="text">

$opts['max'] should be 20 instead of default 10 in your case in Lines 282 to 287 of includes/ui/ui_lists.inc:

        $edit_entry = "<input $disabled type='text' name='$search_box' id='$search_box' size='".
            $opts['size']."' maxlength='".$opts['max'].
            "' value='$txt' class='$class' rel='$name' autocomplete='off' title='"
            .$opts['box_hint']."'"
            .(!fallback_mode() && !$by_id ? " style=display:none;":'')
            .">\n";