Sage 100

 View Only

  • 1.  Sage 100 export to Excel crashes

    Posted 02-14-2019 15:23
    We've noticed this happening on several clients and in our office, RD Server running Windows 2016 and Windows 10 workstations, for any report when export is chosen, MS Excel Workbook Data-Only and Destination as Application is picked with the default Excel Format Options, we get an error 'Sage 100 has stopped working' and the debug option shows ' An unhandled Microsoft .NET framework exception occured in pvxwin32.exe (18304).  I'm not exporting from preview.  If we change Destination to disk, and save the xlsx file, that works.  If we export to Microsoft Excel (97-2003) Data Only with Destination as Application, that works but client doesn't want it to be an xls workbook due to the 65,536 line limit.  Client is asking why exporting to application no longer works.  I have a call in to Sage support, too.  Thanks.

    ------------------------------
    Mary Mays
    Professional Software, Inc.
    ------------------------------


  • 2.  RE: Sage 100 export to Excel crashes

    Posted 02-14-2019 15:29

    Mary – when you find out the answer, would you let us know?  Sure enough, that's been happening  to our clients who have to export data out of Sage 100 Payroll for a new Statewide Tax we have.

     

    Thanks!

    Sue

     

    Sue Bennett | President

    P. 503 620 3484 | F. 503 620 2765

    12559 SW 69th Ave | Tigard, OR  97223

    Sue@benpor.com | www.benpor.com

    Bennett/Porter Blog | facebook | twitter

     

     



    ------Original Message------

    We've noticed this happening on several clients and in our office, RD Server running Windows 2016 and Windows 10 workstations, for any report when export is chosen, MS Excel Workbook Data-Only and Destination as Application is picked with the default Excel Format Options, we get an error 'Sage 100 has stopped working' and the debug option shows ' An unhandled Microsoft .NET framework exception occured in pvxwin32.exe (18304).  I'm not exporting from preview.  If we change Destination to disk, and save the xlsx file, that works.  If we export to Microsoft Excel (97-2003) Data Only with Destination as Application, that works but client doesn't want it to be an xls workbook due to the 65,536 line limit.  Client is asking why exporting to application no longer works.  I have a call in to Sage support, too.  Thanks.

    ------------------------------
    Mary Mays
    Professional Software, Inc.
    ------------------------------


  • 3.  RE: Sage 100 export to Excel crashes

    Posted 02-14-2019 15:44
    I've seen this off and on for years.  My recommendation to whoever asks is to go with Disk and leave it at that.  A couple extra clicks is not a big deal, and it works.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 4.  RE: Sage 100 export to Excel crashes

    Posted 02-14-2019 16:30
    +1 @Kevin Moyes​​, as it can be very frustrating to try and resolve it.  But if interested, do some searches in 90 Minds because there's previous threads on this topic.  Here's one for example.

    ------------------------------
    - Brett
    ------------------------------

    Original Message


  • 5.  RE: Sage 100 export to Excel crashes

    Posted 02-18-2019 10:19

    From Sage support – as long as it works if you select DISK, use that format. (exactly the same advice I got from Kevin Moyes)  Said 'Sage cannot guarantee compatibility for exports to all formats under all operating systems.'  They can't duplicate it on their Sage 2018 on a Win 10 client exporting to Office 365 Excel.   I was able to create a custom crystal report  OUTSIDE of Sage and export to MS Excel workbook to application and it worked.  Sage support wonders if it is the reports that use worktables that are having issues exporting to application.  I will contact client and see what report they are running to see if I can create a crystal report, but I doubt that will be a good solution.  I'll just tell them to choose disk.

     

    He will write something up for the Sage KB.

     

    Mary Mays

    Professional Software, Inc. 

    DSD Wichita, Inc.

    800 East First Street, Suite 150 Wichita, KS  67202

    phone: (316)269-4264   fax: (316)269-0512

     

             

     

     

    This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify mmays@pskansas.com immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

     



    ------Original Message------

    I've seen this off and on for years.  My recommendation to whoever asks is to go with Disk and leave it at that.  A couple extra clicks is not a big deal, and it works.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------


Related Content