Sage 100

I'm going to try Sage Support on this tomorrow, even though they'll likely tell me to work with Scanco, but I'm hoping someone might have an idea where to start. After migrating data from Sage 2016 Standard to Sage 2018.6 Premium and then converting, I find that I do not have an "SO_SalesOrderDetail" table at all, and the SQL Conversion Log shows  "Unable to open SQL table: Error #12: File does not exist (or already exists)" only for that table. I've rebuilt all SO key files in v2016 and tried migrating/converting again, but no luck. And I notice the same problem with all companies that have SO activated, so that leads me to believe that it is program-related and not company-specific. Sage KB ID: ID:36813 references problems with 3rd-party products, but I had Ron Jacobs from Scanco on with me earlier and he did not want to go near it. Any suggestions on something else I could try, even if it's to prove that it is Scanco Multi-Bin? Thanks in advance!

------------------------------
Amber Prayfrock, Blytheco
------------------------------

This sounds like the Scanco issue several of us have run into. At least yours gave an Error 12 so you presumably can fix the dictionary and do the migration / conversion again. Do the following:

1. File > Run > SYZCON
2. At the prompt type DD and press Enter
3. Data Dictionary Maintenance should.
4. For Table Name, type SO_SalesOrderDetail or look it up
5. Click on the Custom Info button to bring up the "MAS90 File Header Extensions" window
6. The box for "SQL Create Table" should be checked even on a non-Premium system but I bet it's not. I'll also bet the ProvideX file SO_SalesOrderDetail got created instead.

At this point you can take screenshots and send it to Ron (but don't tell him I sent you !). But if you choose to check the SQL box and Accept then Exit button from main screen this is the subsequent command you can type while at the prompt:

? %sys_ss'CreateTable("SO_SalesOrderDetail","COMPANY:ABC")

Substitute ABC with your actual company, press Enter, then verify the SQL table got created. You can now delete the pvx table with same name. Now use the up arrow to repeat the previous command and change to the next company with S/O data.

Good morning Alnoor - Of course you are right about the "SQL Create Table" checkbox and the SO_SalesOrderDetail ProvideX table. I have run the DD updates and am trying migration/conversion again. And I will save these steps for live upgrade. Do you think Scanco needs to see this screenshot of Data Dictionary Maintenance for any reason? Is this their issue?

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 10-17-2019 22:35
From: Alnoor Cassim
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

This sounds like the Scanco issue several of us have run into. At least yours gave an Error 12 so you presumably can fix the dictionary and do the migration / conversion again. Do the following:

1. File > Run > SYZCON
2. At the prompt type DD and press Enter
3. Data Dictionary Maintenance should.
4. For Table Name, type SO_SalesOrderDetail or look it up
5. Click on the Custom Info button to bring up the "MAS90 File Header Extensions" window
6. The box for "SQL Create Table" should be checked even on a non-Premium system but I bet it's not. I'll also bet the ProvideX file SO_SalesOrderDetail got created instead.

At this point you can take screenshots and send it to Ron (but don't tell him I sent you !). But if you choose to check the SQL box and Accept then Exit button from main screen this is the subsequent command you can type while at the prompt:

? %sys_ss'CreateTable("SO_SalesOrderDetail","COMPANY:ABC")

Substitute ABC with your actual company, press Enter, then verify the SQL table got created. You can now delete the pvx table with same name. Now use the up arrow to repeat the previous command and change to the next company with S/O data.

Glad it worked out! Prudy it is their issue and you should send a screenshot of it with the box unchecked and tell them "My developers tell me this box should always be checked even on a Standard / Advanced system just like all the rest of the Sage standard tables". They know you guys are MDs / DPs so it's better for you in that context.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------

Original Message:
Sent: 10-18-2019 05:06
From: Amber Prayfrock
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

Good morning Alnoor - Of course you are right about the "SQL Create Table" checkbox and the SO_SalesOrderDetail ProvideX table. I have run the DD updates and am trying migration/conversion again. And I will save these steps for live upgrade. Do you think Scanco needs to see this screenshot of Data Dictionary Maintenance for any reason? Is this their issue?

------------------------------
Amber Prayfrock, Blytheco
------------------------------


Original Message:
Sent: 10-17-2019 22:35
From: Alnoor Cassim
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

This sounds like the Scanco issue several of us have run into. At least yours gave an Error 12 so you presumably can fix the dictionary and do the migration / conversion again. Do the following:

1. File > Run > SYZCON
2. At the prompt type DD and press Enter
3. Data Dictionary Maintenance should.
4. For Table Name, type SO_SalesOrderDetail or look it up
5. Click on the Custom Info button to bring up the "MAS90 File Header Extensions" window
6. The box for "SQL Create Table" should be checked even on a non-Premium system but I bet it's not. I'll also bet the ProvideX file SO_SalesOrderDetail got created instead.

At this point you can take screenshots and send it to Ron (but don't tell him I sent you !). But if you choose to check the SQL box and Accept then Exit button from main screen this is the subsequent command you can type while at the prompt:

? %sys_ss'CreateTable("SO_SalesOrderDetail","COMPANY:ABC")

Substitute ABC with your actual company, press Enter, then verify the SQL table got created. You can now delete the pvx table with same name. Now use the up arrow to repeat the previous command and change to the next company with S/O data.

I did send it but they're not owning up to it yet :)

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 10-18-2019 12:57
From: Alnoor Cassim
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

Glad it worked out! Prudy it is their issue and you should send a screenshot of it with the box unchecked and tell them "My developers tell me this box should always be checked even on a Standard / Advanced system just like all the rest of the Sage standard tables". They know you guys are MDs / DPs so it's better for you in that context.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------


Original Message:
Sent: 10-18-2019 05:06
From: Amber Prayfrock
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

Good morning Alnoor - Of course you are right about the "SQL Create Table" checkbox and the SO_SalesOrderDetail ProvideX table. I have run the DD updates and am trying migration/conversion again. And I will save these steps for live upgrade. Do you think Scanco needs to see this screenshot of Data Dictionary Maintenance for any reason? Is this their issue?

------------------------------
Amber Prayfrock, Blytheco


Original Message:
Sent: 10-17-2019 22:35
From: Alnoor Cassim
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

This sounds like the Scanco issue several of us have run into. At least yours gave an Error 12 so you presumably can fix the dictionary and do the migration / conversion again. Do the following:

1. File > Run > SYZCON
2. At the prompt type DD and press Enter
3. Data Dictionary Maintenance should.
4. For Table Name, type SO_SalesOrderDetail or look it up
5. Click on the Custom Info button to bring up the "MAS90 File Header Extensions" window
6. The box for "SQL Create Table" should be checked even on a non-Premium system but I bet it's not. I'll also bet the ProvideX file SO_SalesOrderDetail got created instead.

At this point you can take screenshots and send it to Ron (but don't tell him I sent you !). But if you choose to check the SQL box and Accept then Exit button from main screen this is the subsequent command you can type while at the prompt:

? %sys_ss'CreateTable("SO_SalesOrderDetail","COMPANY:ABC")

Substitute ABC with your actual company, press Enter, then verify the SQL table got created. You can now delete the pvx table with same name. Now use the up arrow to repeat the previous command and change to the next company with S/O data.

The data appears good now after another full migration and conversion, and I was able to run the Scanco Prepare Data without any errors. Thank you so much, Alnoor!!

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 10-17-2019 22:35
From: Alnoor Cassim
Subject: Sage Std to Prem Data Conversion - Unable to open SQL table

This sounds like the Scanco issue several of us have run into. At least yours gave an Error 12 so you presumably can fix the dictionary and do the migration / conversion again. Do the following:

1. File > Run > SYZCON
2. At the prompt type DD and press Enter
3. Data Dictionary Maintenance should.
4. For Table Name, type SO_SalesOrderDetail or look it up
5. Click on the Custom Info button to bring up the "MAS90 File Header Extensions" window
6. The box for "SQL Create Table" should be checked even on a non-Premium system but I bet it's not. I'll also bet the ProvideX file SO_SalesOrderDetail got created instead.

At this point you can take screenshots and send it to Ron (but don't tell him I sent you !). But if you choose to check the SQL box and Accept then Exit button from main screen this is the subsequent command you can type while at the prompt:

? %sys_ss'CreateTable("SO_SalesOrderDetail","COMPANY:ABC")

Substitute ABC with your actual company, press Enter, then verify the SQL table got created. You can now delete the pvx table with same name. Now use the up arrow to repeat the previous command and change to the next company with S/O data.