@Madeline Stefanou sorry for the confusion. It turned out the value of 1000000 was not the issue. I jumped to that conclusion prematurely. The variable holding that index value was actually a counter in an endless loop and its last value when it got the Error 43 was 1000000 simply because it was trying to format 7 digits into 6 digits. The real problem was a line index in IMO (not IM0 the options file) was circularly pointing back to itself causing the endless loop.
IOW, on v4.05 I DFDM'd IMN the Sales Kit Header file and typed in the Kit Number of KZ12345 (something like that). You might remember from the old days the 1st numeric field we see in DFDM is Field 2 (what Sage called IMN[0] ) and was set to 26907 (this came from a variable after clicking on Debug button in the error). This number is called the Link-In value. It represents the kit's line index for the 1st component line.
I DFDM'd IMO the Sales Kit Detail file and typed in 26907. That brought me to the first line of this kit. Here, like any other (blasted) index file, Field 2 from DFDM represents the previous index we came from, aka "Link from Prev" which should say 0, since this was the 1st line. Field 3 represents the next component's line index, aka "Link to Next", and if this happened to be our last kit line, it should say 0.
However, it had issues.
- It was a comment line instead of a component item. Weird to see that as the only line in a kit.
- Field 2 the Link from Prev, and Field 3 the Link to Next, both of them were set to 26907 instead of both set to 0. At this point, I realized the circular reference was causing the conversion program to process in an endless loop and would have just hung forcing us to kill the task if it was not for the coincidental Error 43 --> Data corruption!
I DFDM'd IMN and deleted the KZ12345 record. This destroyed the link to IMO. Effectively that fixed it. Then ran Analyze and Relink on IMO. It found 16 errors to fix. We restarted the conversion after dealing with some permissions issues and got past the problem area. I stuck around to make sure it completed.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------
Original Message:
Sent: 12-23-2025 09:37
From: Madeline Stefanou
Subject: Error converting from v4.x to v2017, can't get past
@Jeff Schwenk in 4.05, they used Indexed Files. In the conversion on the way up, in v4.40 it started to use Sales Kit Detail Line Indexes of 6-digit max. Somehow in the conversion it created line key indexes of more than 6-characters (probably some type of corruption). When it fails at the v4.40 portion; the indexes need to be corrected if they exceed 6-digits, then the conversion can proceed.
------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------
Original Message:
Sent: 12-23-2025 09:24
From: Madeline Stefanou
Subject: Error converting from v4.x to v2017, can't get past
a bit like "whisper down the lane" since I was not involved last night when it was corrected. Alnoor and our team member spent about 90-minutes working through data. I believe the Line Key in Sales Kit Maintenance Detail was set at larger than 7-character; and that was part of the issue. In older versions the key could be larger but on v4.xx + it is set to 6-characters.
------------------------------
Madeline Stefanou
RKL eSolutions, LLC
Original Message:
Sent: 12-23-2025 09:17
From: Jeff Schwenk
Subject: Error converting from v4.x to v2017, can't get past
What was the solution?
------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444
Improving bottom lines for over 25 years!
Original Message:
Sent: 12-23-2025 09:15
From: Madeline Stefanou
Subject: Error converting from v4.x to v2017, can't get past
With the help from @Alnoor Cassim our team got past this error on the way from 4.05 to 4.50... Thank you Alnoor!
------------------------------
Madeline Stefanou
RKL eSolutions, LLC