We just tried your suggestion in the SQL version.
Basically ran the conversion and let it get stuck then cancelled the conversion process in task manager.
Went to the SQL database tools and renamed the file. We did not create a blank file
Restarted the conversion and picked up from where it left off. It did not create a new file by itself.
Back to the SQL database tools and renamed the file back.
We did a comparison and we could see that it added about three new data fields which were all populated with NULL values. One had to do with expiration dates and the other for parent quantities and items (not sure what those were all about but since they are new, they really shouldn't have anything in them anyway).
So far testing seems to show everything working but we're going to watch it like a hawk while we do our due diligence before going live.
Thanks for your input Beth.
------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.
Spokane Valley WA
------------------------------
Original Message:
Sent: 09-23-2020 14:41
From: Beth Bowers
Subject: 2020 conversion
DOH, I wasn't too clear about that, was I? I renamed, then created a new blank file, converted, then renamed the original file back. Ran the History report again and got the same data.
------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------
Original Message:
Sent: 09-23-2020 13:54
From: Thomas Rogers
Subject: 2020 conversion
Unfortunately in my situation the file is big.
Wonder if it might be possible to backup the individual table, clear it and then restore it from the backup?
So did you reinitialize the file? Or just rename it so it couldn't be found. I would think it would error out if the file could not be found during the conversion.
------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.
Spokane Valley WA
Original Message:
Sent: 09-23-2020 13:32
From: Beth Bowers
Subject: 2020 conversion
(Shh) - I checked and saw the 1) the file was the same size and key was the same between the versions and 2) I knew the customer hadn't used Lot/Serial much. (The report is only 7 pages long of all history.)
So I renamed the file and finished the conversion, then renamed the file back. It's been a week and no issues.
But it wasn't Premium, so I could get away with that.
------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
Original Message:
Sent: 09-23-2020 13:04
From: Thomas Rogers
Subject: 2020 conversion
I'm doing one right now that is having that problem with 2020 premium..
I'm on a second run through right now but I suspect I will get the same result. Client has a historical backup company that I plan to try it on if I get the same issue. Hopefully that will determine if it is a data issue.
I had this with another client put it was the AR_CASHRECEIPTS_HISTORY file. Tech support corrected a problem in the data dictionary and resolved it. I'm suspecting something similar for this.
Any resolution yet? Have you talked with Sage Tech Support?
------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.
Spokane Valley WA
Original Message:
Sent: 09-21-2020 17:52
From: Wayne Schulz
Subject: 2020 conversion
My next big UG is going to have lot/serial but no others yet.
---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990