Search options (Page 86 of 246)

Thanks @Foxyhimself and @bazza.
Fix committed.

Allocation may have been made so you should not change the Customer name/branch. Void it and recreate it anew. Database intervention is possible but not advised.

You need to close the fiscal years in sequence from the earliest onwards.

The British CoA (among others) is broken as far as order of fields in some tables are concerned. The Official pkg repo has not been updated. Check with the schema of the en_US-new.sql.
Have a look for corrected one here.

DacEasy (v9 and v10 to 14 and Utilities) when I last used it over 2 decades ago was using dBASE (.DBF) files. It should be trivial to export them out into Excel / CSV files before importing them into MySQL directly. DacEasy last used BTRIEVE database for DOS that is akin to MySQL's ISAM (Indexed Sequential Access Method) DB Engine.

The manual for DacEasy v14 is available here and it's list of files and what they are for is listed here.

Commercial products to convert Btrieve DB to MySQL DB are:
Mertech Btrieve to MySQL
FullConvert Enterprise - abandoned / unsupported / lost on the web
Nelson Software Tools

BTrieve itself is now Pervasive SQL (PSQL) - MySQL Discussion thread for conversion.

DacEasy is now part of Sage and they do not generate Activation keys for these old versions when you need to re-install. Provide feedback if this works.

If you are interested in still using DacEasy, it can be setup in a DOS emulator and run on the newer OSes along with an LPT2USB Driver for them.

Capturing LPT1 is also possible.

FreeDOS supports USB Printers.

You can also run DacEasy in a DOS VirtualBox / VMWare Player / QEMU Emulator.

DOSBox too can be used.

Which Chart of Accounts are you using? Update FA to the latest codebase and try.

The said error can come in when the "Preferences" link (Setup => Display Setup) cannot be saved since there would have been no Profit & Loss Account defined or defined wrongly (line 66 of admin/gl_setup.php).

This error can also come when a fiscal year is closed without any Profit & Loss Account defined as seen in line 137 of admin/db/fiscalyears_db.inc.

Assume you are using FA 2.4.x.

Which Chart of Accounts did you start with?

@joe / @ itronics: can commit this.

Yes, there is no file uploaded since the $_FILES is empty on upload. The $_REQUEST is like:

Array
(
    [comments] => 
    [comp] => no
    [protect] => 1
    [uploadfile] => frontac24_1_1_20171206_1551.sql
    [upload] => Upload file
    [_focus] => comments
    [_modified] => 0
    [_confirmed] => 
    [_token] => pZNU0jkQsPSi05HaQyLGAQxx
    [FA9d3e45269bea7dab23238a920d251e93] => 33ebcyesul0lgdnms17d8nna35
)

The $_POST array does not have the last element above.

The fix is to make the start_form a multipart one - it was inadvertently changed during the last commit to this file.
Change line 190 in admin/backups.php

start_form(false, true);

to be:

start_form(true, true);

Setup => Company Setup => Login Timeout (time in seconds)

Also checkout lines 425-432 of includes/session.inc:

/*
    Uncomment the setting below when using FA on shared hosting
    to avoid unexpeced session timeouts.
    Make sure this directory exists and is writable!
*/
// ini_set('session.save_path', VARLIB_PATH.'/');

ini_set('session.gc_maxlifetime', 36000); // 10hrs

Rather than change the function, change it to a call to another function by making line 135 in fixed_assets/process_depreciation.php:

  check_db_has_stock_items('There are no active fixed asset defined in the system.');

to be:

   check_db_has_depreciable_fixed_assets('There are no active fixed asset defined in the system.');

@joe: commit if okay.

Is it that you want to change the item itself in say an invoice or sales order? Editing them are available in FA.

After you have made transactions using one item code, you cannot change the item code in the stock_master, but you can change it's name description to suit the correct one. You can also make a new item code for another item and then edit the old transactions accordingly. The item_code like the stock_id are identifying keys in the tables and foreign keys in others like the transaction tables.

MySQL and dBASE III / FoxPro are the same as far as data storage visibility are concerned. Only the relations are set in the sql command in MySQL. The relations are set as separate statements in dBASE III / FoxPro in the operational area.