FrontAccounting forum — Upgrading

Re: Upgrading

2020-04-01T23:27:11Z

In FA 2.4.8>Setup>Transactions References> I set the Pattern = 1500 for Traction Type = Journal Entry. I then created two Journal Entries Trial 1 and Trial 2. Trial 1 was a $27 Debit into Petty Cash from Club Dues, and Trial 2 was a $15 Debit into the Savings Account from Raffle Ticket Sales. Immediately after entering the second JE, I did a Journal Inquiry and a GL Inquiry with the results below.

Journal Inquiry:
Date    Type    Trans # Counterparty Reference Amount Memo
04/01/2020 Journal Entry 1079    1500    54.00 Timothy Goolsby - Key #82 - Sale & Deposit
04/01/2020 Journal Entry 1080    1501    30.00 John Davis - Irish Visitor - MVMAC Hat

Editing Trans 1079:
Account Code Account Description Dimension Debit Credit Memo
1065    Petty Cash    20.00 Timothy Goolsby - Key #82 - Sale & Deposit
4025    Sale of Gate Keys    5.00    Timothy Goolsby - Key #82 - Sale
2442    Gate Key Deposits Liability       15.00 Timothy Goolsby - Key #82 - Deposit
1065    Petty Cash    27.00 trial 1
4445    Club Dues       27.00    trial 1
Search GL accounts
Add Item
Total 47.00 47.00

Editing Trans 1080:
Account Code Account Description Dimension Debit Credit Memo
1065 Petty Cash    11.00 John Davis - Irish Visitor - MVMAC Hat
4010    Sales of Caps, T-Shirts, etc.    11.00 John Davis - Irish Visitor - MVMAC Hat
1061    Savings Account    15.00 trial 2
4448    Income from Raffles    15.00 trial 2
Search GL accounts
Add Item
Total 26.00 26.00

GL Inquiry:
Type # Reference Date Account Dimension Person/Item Debit Credit Memo
Journal Entry 1079 1500 04/01/2020 1065 Petty Cash    27.00 trial 1 Edit
Journal Entry 1079 1500 04/01/2020 4445 Club Dues    27.00 trial 1 Edit
Journal Entry 1080 1501 04/01/2020 1061 Savings Account 15.00 trial 2 Edit
Journal Entry 1080 1501 04/01/2020 4448 Income from Raffles       15.00 trial 2 Edit

Note
1. The Journal Inquiry again shows multiple JE's for each Reference transaction 1500 and 1501
2. The total for each JE on the Edit screen is different than that shown in Journal Inquiry listing -
$47 vs $54 for Ref 1500
$26 vs $30 for Ref 1501
3. The Listing for the GL Inquiry gives the correct information for both JE's.

Any ideas as to what is going on?

Re: Upgrading

2020-04-01T10:31:24Z

When upgrading from 2.3.x to 2.4.x, you need to set the default pattern for numbering the references to match for compatibility unless you are starting afresh where the latter's defaults are okay.

Re: Upgrading

2020-03-27T21:06:08Z

A couple of questions have arisen after the upgrade from 2.3.26 to 2.4.8. When I do Journal Inquiry over the last default dates, 2.4.8 gives

03/21/2020 Journal Entry 1069 658 432.21 Al Siegwart - Chk #1290 - Miscellaneous Training and Club Expenses
- Trainer airplane + AMA Club 1-Yr Fee Savings Account - IOD
Interest Earned

When I go to edit it to check the details for Check #1290 and Interest earned, I get

1070 PayPal       36.01 Jack Fitzpatrick - 2020 Dues - PayPal
4445 Club Dues       36.01 Jack Fitzpatrick - 2020 Dues - PayPal
1060 Checking Account    432.03 Al Siegwart - Chk #1290 - Miscellaneous Training and Club Expenses
5687 AMA Expenses       100.00 Al Siegwart - Chk #1290 - Miscellaneous Training and Club Expenses
5614 Training Expenses    332.03 Al Siegwart - Chk #1290 - Miscellaneous Training and Club Expenses
1061 Savings Account    0.18 Savings Account - IOD Interest Earned
4440 Interest from Savings Account    0.18 Savings Account - IOD Interest Earned

That is, the Trans # 1069/Reference 658 really refers to 3 Journal Entries - one for Check #1290, one for membership dues for Jack Fitzpatrick, and one for the Interest paid on the savings account.

When I run the same Journal Inquiry in 2.3.26 I get 3 separate Journal Entries -

02/26/2020 Journal Entry 1069 1056 36.01 Jack Fitzpatrick - 2020 Dues - PayPal
02/26/2020 Journal Entry 1068 1055 432.03 Al Siegwart - Chk #1290 - Miscellaneous Training and Club Expenses -
Trainer airplane + AMA Club 1-Yr Fee
03/02/2020 Journal Entry 1085 1072 0.18 Savings Account - IOD Interest Earned

Which brings me to my question: What is the "Reference" number? In looking at the Journal Inquiries I see that the reference number is the same as older Tran #'s. I'm trying to figure out whether the updated 2.4.8 database accurately reflects the 2.3.26 data going back to 2012. The Balance Sheet shows the same totals, and the GL Inquiry shows all of the same Journal Entries as between 2.3.26 and 2.4.8. Why is the Journal Inquiry goofed up?

Re: Upgrading

2020-03-17T17:32:21Z

Rereading my last post, understand that all 44 lines mentioned in the error log were commented out. After that, the update took quite a while but eventually worked.

Seems like this should also work for Iffig...

Re: Upgrading

2020-03-17T17:23:18Z

good to hear it.

Re: Upgrading

2020-03-17T17:11:17Z

kvvaradha, I took the approach mentioned in your last paragraph, editing the alter2.4.sql file. I opened it in a text editor and made each of the lines mentioned in the log file a comment by inserting '* rjp ' at the beginning. Thus line 30 became

# rjp ALTER TABLE `0_tax_group_items` ADD COLUMN `tax_shipping` tinyint(1) NOT NULL default '0' AFTER `rate`;

Similarly, lines 36 and 37 became

# rjp ALTER TABLE `0_sales_order_details` ADD KEY `stkcode` (`stk_code`);
# rjp ALTER TABLE `0_purch_order_details` ADD KEY `itemcode` (`item_code`);

This modification allowed me to update the software without errors

Re: Upgrading

2020-03-11T05:56:31Z

Looks like full mess up with your existing database. Because it looks like the database already has the columns what we introduced new in the version 2.4 in your 2.3.26. So it looks like some of the db changes you have already done. That's giving trouble now.

My way for you to fix it.

1. Just export the exact database you have in 2.3.26 and keep it.
2. Download a new version 2.4.8 and extract it in separate directory. And from the files, open FA directory/sql/en_US-new.sql
3. Use a version comparison software and compare both sql files. And bring the missing changes to your existing version and which will help you to fix the problem.

Note: You need some sql query knowledge to fix it.

The other way is edit the alter2.4.php and alter2.4.sql files inside sql directory. With that you can remove the changes of duplicate fields. And try again to update.

Re: Upgrading

2020-03-10T23:40:01Z

Experience similar to Iffig - updating from 2.3.26 to 2.4.8 on Windows 10 Wamp server. Followed the steps outlined by kvvaradha. When I log as administrator in the company "0" and do a software upgrade, the process fails. I get the following error messages:

30:Duplicate column name 'tax_shipping'
36:Duplicate key name 'stkcode'
37:Duplicate key name 'itemcode'
39:Duplicate column name 'bank_account'
41:Duplicate column name 'tax_included'
45:Duplicate column name 'bank_charge_act'
48:Duplicate column name 'transaction_days'
50:Duplicate column name 'prep_amount'
51:Duplicate column name 'alloc'
53:Duplicate column name 'prep_amount'
54:Duplicate column name 'alloc'
59:Duplicate column name 'invoiced'
68:Duplicate column name 'prep_amount'
79:Duplicate column name 'no_purchase'
80:Duplicate column name 'dflt_no_purchase'
83:Duplicate column name 'rate'
86:Duplicate column name 'save_report_selections'
87:Duplicate column name 'use_date_picker'
88:Duplicate column name 'def_print_destination'
89:Duplicate column name 'def_print_orientation'
143:Duplicate column name 'dimension_id'
144:Duplicate column name 'dimension2_id'
151:Duplicate column name 'usage'
152:Duplicate column name 'memo'
155:Duplicate column name 'person_id'
159:Duplicate column name 'person_id'
199:Duplicate column name 'reg_type'
255:Can't DROP 'branch_code'; check that column/key exists
256:Can't DROP 'SupplierID_2'; check that column/key exists
257:Can't DROP 'type'; check that column/key exists
260:Duplicate column name 'fixed_asset'
273:Duplicate column name 'depreciation_method'
274:Duplicate column name 'depreciation_rate'
275:Duplicate column name 'depreciation_factor'
276:Duplicate column name 'depreciation_start'
277:Duplicate column name 'depreciation_date'
278:Duplicate column name 'fa_class_id'
279:Unknown column 'actual_cost' in '0_stock_master'
288:Duplicate column name 'unit_cost'
289:Unknown column 'std_cost' in '0_wo_requirements'
291:Can't DROP 'last_cost'; check that column/key exists
294:Unknown column 'assembly_account' in '0_stock_master'
295:Unknown column 'dflt_assembly_act' in '0_stock_category'
308:Unknown column 'counter' in '0_budget_trans'

Lots of errors to fix, but I don't know where to start. Please give me some ideas.

Re: Upgrading

2019-04-14T09:15:58Z

I have a problem to update the database after migrating and upgrading from FA2.3.26 (on a webhost) to FA2.4.6 (on Xampp).
first I can't upload my back-up file so I copied it into the company/backup folder
The theme is set to default, the company name is same and the Table Pref is the same in the two versions.
When I log as administrator in the company "0" and do a software upgrade, the process fails. The "current version" number is changed to "2.3rc". The "last log" shows:

Upgrade log for company '4'
[14-Apr-2019 10:39:45 Europe/Berlin] [Info] Upgrade started for company 4.
[14-Apr-2019 10:39:52 Europe/Berlin] [Info] Security backup in file ../company/4/backup/erdai149_fron989_4_20190414_1039.sql done.
[14-Apr-2019 10:41:07 Europe/Berlin] [Error] 30:Duplicate column name 'tax_shipping'
[14-Apr-2019 10:41:07 Europe/Berlin] [Error] 36:Duplicate key name 'stkcode'
......
[14-Apr-2019 10:41:07 Europe/Berlin] [Error] 97:Duplicate entry 'print_item_images_on_quote' for key 'PRIMARY'
[14-Apr-2019 10:41:07 Europe/Berlin] [Error] 98:Duplicate entry 'default_receival_required' for key 'PRIMARY'
[14-Apr-2019 10:43:02 Europe/Berlin] [Info] Upgrade failed. Original database content restored successfully.
[14-Apr-2019 10:43:04 Europe/Berlin] [Info] Upgrade for company 4 finished.

Help would be very much appreciated.
Thanks
Iffig

Re: Upgrading

2019-04-13T19:58:36Z

When I was comparing my database to the FA2.4 I found a number of fields had different default values and such, so I felt it might be better if I make my DB conform to the exact same structures of demo data.

So here is what I ended up doing:
1. Exported my data with phpMyAdmin keeping Just the Data and truncating the tables (as opposed to dropping them)
2. I created a fresh DB and imported the 2.3.26 demo data with phpMyAdmin (my system was FA2.3.16)
3. I imported my Data Only with phpMyAdmin
4. I then logged into an admin account of my DB and did a Software Update

All appears to be well.

The same steps could work for an FA2.4 db clean up as well

Tom

Re: Upgrading

2019-04-13T11:03:23Z

You may be in the main menu section. Try to open sub module pages like direct invoice. It will prompt the message. Or you can directly goto setup-> software updates. There you can see update option available

Re: Upgrading

2019-04-13T10:51:19Z

Is this statement correct?

7. Now when you login as administrator, FA will ask you to update your database.

I loaded the demo data from 2.3.26 into my 2.4.6 install and FA does not ask me to update my DB.

I can go do the update, but it never asks me.
What triggers this question from the code?

Is there something missing from mt DB?

Tom

Re: Upgrading

2019-04-12T15:21:17Z

@tom - I forget the reason for it. But all these steps will help you to update database.if yoy have backup. Then go with test instance and try them.

Re: Upgrading

2019-04-11T11:23:24Z

After a detailed look at my database I have found that he difference between my tables (2.3.16) and 2.3.26 are that 3 fields are out of order.
Seems they were added to the end not in the middle.

There are also many defaults that are different.

I am wondering if I could export my DATA only and import into the 2.3.26 tables (truncating the tables before inserting)

It seems that could work, unless I am missing anything obvious

Thoughts?
(Yes everything is backed up so total failure is not a real problem)

Re: Upgrading

2019-04-10T02:45:14Z

Not phpmyadmin
it's all through FA.