This is what the event viewer shows. Not sure how to interpret it so I will ask Dr Google and see if she knows.
Log Name: Application
Source: Application Error
Date: 10/5/2019 2:54:13 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MCSSB
Description:
Faulting application name: pvxwin32.exe, version: 9.61.25.0, time stamp: 0x5c37913a
Faulting module name: msoshext.dll, version: 16.0.12026.20060, time stamp: 0x5d696132
Exception code: 0xc0000005
Fault offset: 0x0008b8fa
Faulting process id: 0x1b08
Faulting application start time: 0x01d57bb69dd991c2
Faulting application path: C:\Sage\Sage100v61\MAS90\Home\pvxwin32.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\msoshext.dll
Report Id: f4e48b1b-cf41-428d-bd3d-a057bcec1f18
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-10-05T19:54:13.516606900Z" />
<EventRecordID>78568</EventRecordID>
<Channel>Application</Channel>
<Computer>MCSSB</Computer>
<Security />
</System>
<EventData>
<Data>pvxwin32.exe</Data>
<Data>9.61.25.0</Data>
<Data>5c37913a</Data>
<Data>msoshext.dll</Data>
<Data>16.0.12026.20060</Data>
<Data>5d696132</Data>
<Data>c0000005</Data>
<Data>0008b8fa</Data>
<Data>1b08</Data>
<Data>01d57bb69dd991c2</Data>
<Data>C:\Sage\Sage100v61\MAS90\Home\pvxwin32.exe</Data>
<Data>C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\msoshext.dll</Data>
<Data>f4e48b1b-cf41-428d-bd3d-a057bcec1f18</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------
Original Message:
Sent: 10-05-2019 15:13
From: Phil McIntosh
Subject: Unable to Open an .xlxs Memo Attachment
Is here anything in the event log (in Windows) when this happens?
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------
Original Message:
Sent: 10-05-2019 14:58
From: Doug Higgs
Subject: Unable to Open an .xlxs Memo Attachment
Hmmm.. I don't know what the difference could be. I am now waiting for Sage to help me resolve this. I see this issue was reported on Sage City 2 years ago and there was no solution offered. I have re-created the issue on my laptop - Win 10 1809 Sage 100 v 2019.1 standard, Office / Excel 2016 on premise. At the customer site the same issue with Sage 100 2017 or 2019.1 premium, Win 10 1809 and 1903, Office / Excel 365.
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
Original Message:
Sent: 10-05-2019 13:39
From: Dan Burleson
Subject: Unable to Open an .xlxs Memo Attachment
Sorry, but I was using "memo-ed" as a verb. I had no problem loading a ".xlsx" using the Customer Maintenance Memo View Attachment button with 2019 Std and I also tried this on 2019 Premium Workstation at level 1903 as shown in the linked video below:
.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
Original Message:
Sent: 10-05-2019 06:46
From: Doug Higgs
Subject: Unable to Open an .xlxs Memo Attachment
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
Original Message:
Sent: 10-05-2019 02:28
From: Dan Burleson
Subject: Unable to Open an .xlxs Memo Attachment
I don't have this issue on Windows 10 (1809) Sage 100cloud Standard 2019 (Version 6.10.0) loading a memo-ed xlsx in Customer Maintenance.
I assume you mean .xlsx. I use Office 365 and there's no such thing as an .xlxs extension.
------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
Original Message:
Sent: 10-04-2019 10:53
From: John Leonard
Subject: Unable to Open an .xlxs Memo Attachment
Doug, I believe it is an issue with Windows and not a Sage issue per se and something that Microsoft needs to fix.
Original Message------
Thank you @John Leonard Did you open a case with Sage about this issue? This is an important and urgent issue. Windows 7 isn't supported in less than three months. All of the current Windows 10 builds are 1809 or newer. Most people are using Office 365 or a version of Excel that uses xlxs extensions. If the users can attach a file but cannot open it this is a big problema. It also affects third party enhancements.
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------