Search options (Page 11 of 97)

Sure, if you have a chance to install gettext on the server, just do it. gettext works as binary php extension and uses optimized binary *.mo translation files. This is surely less resource consuming than php implementation.
Janusz

No, gettext is optional php module, but when it is active on your server, the server have to support locale defined by FA language extension you have selected, otherwise the translation will not work.
Janusz

If you are asking about whether the wire fee should be paid by customer or put in costs, then I don't know, it depends on agreement and/or local habits.

Technically you can enter wire fee directly in Customer Payment form, and the fee will be included in AR, but subtracted from the amount registered on bank account.

Janusz

There was big Sourceforge site upgrade these days, so the Repo could be unavailable for some time. Now all works as before, but on new  URLs.
Janusz

Practically none. We consider switching to InnoDB only database in next major release as prepartion to foreign keys constraint.
Janusz

Hi Bob,
Consider opening FA Online account on our server. You have technical support included in small monthly subscription.
Janusz

Whether first name, last name or both, as well as the names order strictly depends on local habits. IMHO the only sensible way to fix this problem in FA is providing mail templates in FA.
Janusz

You can comment out line 142 in reporting/includes/header2.inc, then you will have page numbering on all  reports.
Janusz

FA does not have user fields suppot just now, so you are on your own. Most of database  related code is stored in includes/db/* files, so if you want to make use of extra data fields you have to start your changes from here, and continue in user interface files (i.e. those called from main menu).
Janusz

Software Upgrade menu option should be used only in case you want to install new FA version, but the one you have already installed has different major release number, e.g. you want to upgrade from 2.2.xx to 2.3.17. Otherwise it should not be used at all - see upgrade.html instructions.

Force option is last resort which should not be used unless normal upgrade fails. This option is provided here for rare situations when some changes have been done in company database scheme outside FA application control, and normal upgrade process fails.

Janusz

Yes, you are right again. I have finally found the original problem. Simply the calculated exchange rate should not be stored in customer Payment record (bank to home currency is stored here, and not bank to customer currency exrate; this is done later in the code).
I have run a couple of tests covering various currencies combinations on the write_customer_payment function, and now all looks OK (repo updated).
Thank you very much for your help .

Janusz