Search options (Page 225 of 247)

What version of FA are you using. It will need the latest v2.3.15 and the HG updates till 3212 - read the Release Announcement Post.

Also try to disable the .htaccess file in the distribution and troubleshoot the Apache errors thereafter to see what can be accomodated / changed (httpd.conf) in it.

Refer Forum Post

After installing Dashboard Module and Theme, activate the Module for the company desired and enable the Access Roles for all users for Dashboard resource. Then browse to:

http://ip.or.domain/path.to.frontaccounting/modules/dashboard/dashboard_setup.php
and
http://ip.or.domain/path.to.frontaccounting/modules/dashboard/reminder_setup.php

and set up the reminders.

That version is quite old - do not know if any pertinent code for this issue has changed much.

Reverse Journal entry is one way.

Try to upgrade to the recent version with all patches till date.

If you wish to adjust the db manually (not recommended) then do so with care and refer similar issue in the wiki.

Lines 127 to 138 of includes/db_pager.inc:

    //    Change sort column direction 
    //    in order asc->desc->none->asc
    //
    function sort_table($col) 
    {
        $ord = $this->columns[$col]['ord'];
        $ord = ($ord == '') ? 'asc' : (($ord == 'asc') ? 'desc' : '');
        $this->columns[$col]['ord'] = $ord;
        $this->set_page(1);
        $this->query();
        return true;
    }

This clearly shows a $ord check for empty being retained as empty becoming ASC, a check for asc being set to DESC  but if desc, no enforcement is done unless invoked by a click to be ASC. Hence Line 133:

        $ord = ($ord == '') ? 'asc' : (($ord == 'asc') ? 'desc' : '');

should possibly be explicit in all it's redundant splendour  (default being to capture any invalid declaration degrading gracefully) like:

        switch ($ord) {
            case 'asc':
                $ord = 'desc';
                break;
            case 'desc':
            case '':
                $ord = 'asc';
                break;
            default:
                $ord = 'asc';
        }

Hence a setting of 'asc' in the code would result in a default display of DESC in this case as in the earlier one as well. This code fragment does not change any logic and is unnecessary and is placed for an understanding of how activation occurs on clicking only.

If there is a check for an initial value placed in the php page we should use that value to be the default when the $ord is empty thru' clicking route - thereafter, the clicked value of $ord will be available as asc or desc.

Lines 50-62 of includes/ui/db_pager_view.php:

    foreach($pager->columns as $num_col=>$col) {
        // record status control column is displayed only when control checkbox is on
        if (isset($col['head']) && ($col['type']!='inactive' || get_post('show_inactive'))) {
            if (!isset($col['ord']))
                $headers[] = $col['head'];
            else {
                  $icon = (($col['ord'] == 'desc') ? 'sort_desc.gif' : 
                    ($col['ord'] == 'asc' ? 'sort_asc.gif' : 'sort_none.gif'));
                $headers[] = navi_button($pager->name.'_sort_'.$num_col, 
                    $col['head'], true, $icon);
            }
         }
    }

sets the sort image on the header correctly and checks used here can be used in the earlier code fragment to synch a similar behaviour.

Voiding should van(qu)ish the transaction, right?

Try line 268 in sales/inquiry/sales_orders_view.php :

        _("Required By") =>array('type'=>'date', 'ord'=>''),

to be:

        _("Required By") =>array('type'=>'date', 'ord'=>'desc'),

Informed Janusz/Joe to decide on policy and code accordingly:

Info for investigation:

function handle_negative_inventory($stock_id, $quantity, $standard_cost, $date_)
is defined in includes/db/inventory_db.inc

function update_average_material_cost($supplier, $stock_id, $price, $qty, $date, $adj_only=false)
is defined in purchasing/includes/db/grn_db.inc

Or send the company the credit note as well!

The company/# folder may have changes and hence duplication may be in order.

Use OpenVZ Virtual Machines and synch the db and rsync the company folder - no need to change the company # as well and the db backup will be restored faithfully on the training VM.

It is possible that the backup itself had the double records!

It is more a system level db centric update. Rarely changes within a minor version - sometimes a force update may be in order when manually upgrading. If used, use with care after backup.

This is meant for those upgrading from a lower database schema version from older versions of FA. It is not used in fresh installs.