Search options (Page 122 of 246)

It will not be an ERP then. Might as well have ExcelAccounting....

The FrontReport class property $companyLogoEnable needs to be enabled. It is false by default in it's class method Info().

In most if not all reporting/repXXX.php files there will be a line like:

$rep->Info($params, $cols, $headers, $aligns);

Just change it to:

$rep->Info($params, $cols, $headers, $aligns, , ,  true);

The actual prototype for it is:

function Info($params, $cols, $headers, $aligns,
        $cols2 = null, $headers2 = null, $aligns2 = null,
        $companylogoenable = false, $footerenable = false, $footertext = '')

@joe: Should we not have a config file switch for it or atleast a preference setting on a per company basis?

Employee attendance and reports can be done completely outside of FA unless you need to tie in with accounting / salaries.

Try Adminer or Radicore to get it done.

You can choose whichever method by passing the payment voucher or creating the invoice on the appropriate date.

Which features in FA do it automatically that affects the reporting for each method?

Thanks @joe.

@itronics committed it on 2015-07-10.

This now stands cross referenced. The name field / column can be backquoted in the sql.

History transactions will have to be handled by Journal Vouchers to transfer from Cash to appropriate Bank or vice versa depending on how the payment came in and how you "applied" it.

Navigate to Banking and General Ledger -> Bank Accounts and you should see your Cash and Bank Accounts listed there. The Account must first exist in the Accounts Master and then be assigned here.

On creating a customer, you should create a branch for the customer and you must also have items / products / services to sell before you can create an invoice. The branch should be created for the specific customer.

Which version of PHP / MySQL are you using and what platform is the server on?

To start with use the standard default theme whilst importing for first time. Make sure that your db schema matches the fiekd names and types in the same order as the sql/en_US-new.sql file.

Yes, but beware of changing the changed ones. Better make a separate dummy field in each table and sequentially replacing where it is NULL and then dropping the original column, renaming the dummy column to the original column and then enabling the foreign keys when all the tables are done.

If there are only a few entries, manually enter a JV on the last day of the previous fiscal period and open the new fiscal and close the old one.

Otherwise, make one entry in a JV on the last day of the of the previous fiscal period and compare the before and after backups for what has changed and prepare a set of SQL statements for all the others in a spreadsheet and execute them in your MySQL client.

Your PR Requests are for FA 2.3 and FA 2.4. FA 2.3 is retained at MySQL and will not backport MySQLi changes.

Please note that the GitHub repo is just a mirror whilst the actual repo is on SF Git.

@stefan: The changing of the prefix from CHAR to VARCHAR mitigates some cryllic alphabet issues.  Also when the number of characters exceeds 4 or so, the mb_strlen mitigates it.

How will it affect those without mb_strlen (any situations) and whether it can be incorporated wherever strlen is used in both FA 2.3 and 2.4? Any changes here will have to be carried through to everywhere it is used.

Please note that mb_strlen is used in both A 2.3 and 2.4 in the following files:

reporting/includes/class.graphic.inc
reporting/includes/Workbook.php

The usage in the last file above is:

    $strlen = function_exists('mb_strlen') ? mb_strlen($str, 'UTF-16LE') : (strlen($str) / 2);

whilst in the former it is:

    $width = mb_strlen($string, "UTF-8");

@itronics: Using VARCHAR results in slightly bigger memory usage, and slower processing (though probably both issues are hardly noticed).Using VARCHAR results in slightly bigger memory usage, and slower processing (though probably both issues are hardly noticed).

@itronics: Regarding mb_strlen function, it should be used indeed, but it is available only when mbstring php extension is enabled, so to avoid problems the conditional call should be used as it is done in Workbook.php.

References:

* What Every Programmer Absolutely, Positively Needs to Know About Encodings and Character Sets to Work With Text

* php.ini mbstring overload