@apmuthu, @ joe
Based on:- This has been a problem for quite a while
You could assume that:-
Not many users have item desc >50 for purchasing. Those that do have not reported the issue, therefore there is a high likelihood that the purchase order is for internal use only.
So continuing to truncate the supplier_description in the purch_data table would still allow STRICT_ALL_TABLES to be used and most users would see no difference anyway. AND this is no different to what has been happening up to V2.4.6 so far.
So:-
File: \inventory\includes\db\items_purchases_db.inc
21: .db_escape($supplier_description) . ")";
And
File: \inventory\includes\db\items_purchases_db.inc
32: supplier_description=" . db_escape($supplier_description) . "
Could be changed to something like (Not tested):-
File: \inventory\includes\db\items_purchases_db.inc
21: .db_escape(substr($supplier_description, 0, 50)) . ")";
And
File: \inventory\includes\db\items_purchases_db.inc
32: supplier_description=" . db_escape(substr($supplier_description, 0, 50)) . "
Also two changes to function add_or_update_purchase_data in File: \purchasing\includes\purchasing_db.inc Lines 103 & 112
As stated code not tested, so please check.
It's certainly not the correct solution, but does delay db changes to V2.5
The FrontAccounting Wiki(Manual, examples, tips, setup info, links to accounting sites, etc) https://frontaccounting.com/fawiki/