Years ago I was asked about the feasibility of doing the rename via SQL (in a similar circumstance). In the end it didn't go anywhere. The SQL logic isn't just a simple column value change for many tables, where ItemCode is a key column (IM_PeriodPostingHistory, SO_SalesHistory, IM_ItemVendor...). You'd have to intelligently merge the values to handle things "properly".
If you plan to crash and burn, doing the bare minimum, not caring about such tables... be sure to test it to an extreme level to ensure you aren't adding a ticking time bomb to the system. (Eg. if you ever had to run *UTL item quantity rebalancing, would it choke on the inconsistencies?).
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------
Original Message:
Sent: 02-18-2025 08:21
From: Doug Higgs
Subject: Inventory Item Change Process - Possible Alternative
Thanks @Steve Iwanowski I am sure you're right about Sage's official answer being no. Very unfortunate some of these processes haven't been re-worked to take advantage of SQL indexes. We shouldn't have to be writing queries because the software utility was poorly written.
------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------
Original Message:
Sent: 02-18-2025 07:34
From: Steve Iwanowski
Subject: Inventory Item Change Process - Possible Alternative
I'm sure the official answer is No, but I don't see any technical difference (outside the frameworks error checking) in why you couldn't mass update the tables and then rebuild sorts....
------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯