Excel crashing might write something to the Windows Event viewer.  Are you trying to run an existing query or something new?

There is no trace of any issues in Event Viewer. Its more like running the query closes Excel. Its the same query the staff has been running for a long time. The tables are manually selected each time but its always the same.

Has something changed?  Upgrade on Office to 365 Upgrade on Sage 100?

The only thing that has changed is that we apply Windows Updates to all machines every week. This includes all updates for Office products. No updates have been applied to Sage. However I still have 1 (and only one) user that can run the queries. Our office licensing is through VLSC so there is no O365. However I have uninstalled Office on two different machines (different versions of Windows) and reinstalled Office to no avail. Same symptom. Running the query closes (or crashes) Excel.

Try a different table.  It could be bad data (eg. an invalid date).

I've already tried that. Still getting the same symptom.

Instead of clicking Finish, try opening the query in MS Query.

If you get results here, Sage ODBC is fine and you have a problem with your Excel.

Instead of clicking Finish, try opening the query in MS Query.

If you get results here, Sage ODBC is fine and you have a problem with your Excel.

Frank S. Did you ever resolve this issue? I am seeing this error on an upgrade from Sage 100 Standard v2016 to Standard v2020. The workbook w/MS Query updates fine on 2016, but 32-Bit Excel disappears w/o a message or a trace entry in the Event Log when returning the data to a worksheet. Multiple workstations with 32-Bit Excel 2013 (workstation) and 32-Bit Excel 2016 (server) have the issue. Editing and refreshing the query in MS Query works fine, but I encounter this error with simple queries to 4 different tables on the return to Excel. The fact that it doesn't happen with Standard v2016 implies a conflict between 32-Bit Excel and Standard v2020. I cannot recreate on a another Standard v2020 install. Also works fine in Crystal and 32-Bit Power Query on the Standard v2020 install.

FWIW,

I'm running 100 Standard on Windows 10 Pro with the latest Windows updates. My ScriptBasic COM/OLE example that writes data to an Excel spreadsheet still seems to work. I was also able to export a Sales Order from 100 to an Excel spreadsheet. I'm running 100 2020 Standard.

' Excel Example

IMPORT com.sbi
 
oExcelApp = COM::CREATE(:SET, "Excel.Application")
oWorkBook = COM::CBN(oExcelApp, "Workbooks", :GET)
oExcelWorkbook = COM::CBN(oWorkBook, "Add", :CALL)
oExcelSheet = COM::CBN(oExcelWorkbook, "Worksheets", :GET, 1)
FOR i=1 TO 10
  FOR j=1 TO 10
    oCell = COM::CBN(oExcelSheet, "Cells", :GET, i, j)
    COM::CBN(oCell, "Value", :LET, "test-" & i & "-" & j)
    COM::RELEASE(oCell)
  NEXT
NEXT
COM::CBN(oExcelWorkbook, "SaveAs", :CALL, CURDIR() & "\\sbexcel.xlsx")
COM::CBN(oExcelWorkbook, "Close", :CALL)
COM::CBN(oExcelApp, "Quit", :CALL)
 
PRINT "Spreadsheet Created\n"
 
COM::RELEASE(oExcelSheet)
COM::RELEASE(oExcelWorkbook)
COM::RELEASE(oWorkBook)
COM::RELEASE(oExcelApp)

So yes, I did find a solution to this problem.

We moved those users to Windows 10 version 1803 and installed all of the Office updates for Pro Plus 2016. When this was first posted it was affecting all Windows 7 and Windows 10 version 1709 PCs. We never got the combination of Windows 7 + Office 2016 Pro Plus to work with the queries once the issue appeared. Once the users were running 1809 (and later) along with 2016 Pro Plus the issue never came back.

Currently the offices are running SAGE 100 Standard 2017 and 2019 and running great.

Thank you Frank S. for your response. I will check into the specific versions. For the time being, we worked around this by emulating the MS query with a Power Query.