Sage 100

Export to Excel issue is back with 2014 SU4. Have had 2 reports in the past week of errors exporting to Excel. Noticed that the old fix on SU7 for Crystal is no longer available - only SU 9,10, 12. Has anyone seen the error on exporting again and do the higher SUs fix like the old ones? Having to load full Visual Studio - what a PIA. Thought this was fixed....

Beth, I am remoted into a client RDP server and am not having a problem exporting a Customer List to Excel from preview. Just to confirm, they are running Sage 100 vs 2014 Advanced 2014 with PU 4. I ran the default customer list by clicking the print button on the bottom right of the customer maintenance screen. I chose the 'Micosoft Excel Workbook Data-Only' option to Application. In the follow on Options dialog, I chose a 'Minimal' format and left everything else as defaulted. I ran this to disk and to application without any errors. Does that help?

BTW. it is a Windows 2012 RDP server running Office365 Pro Plus.

@ShawnSlavin - has to be a report with a subreport in it

Give me an example and I will check it for you.

I just exported an AP check using the same options above; no errors but not a very good example.

Does have subreport, though. Not sure if it's a good example - AND, they would be on a workstation, not the server... I'll see if they can try a check.

The clients RDP server is a separate server (VM) from the server running Sage 100 so it should be pretty comparable to running from a workstation. Which report are you getting the error with? The module and/or framework may have an impact.

Custom. Had another upgrade this week and same thing - custom report with a subreport in it, exporting to Excel. It's exactly like the error we were getting a year ago and had to load SU 7 from SAP.

Got it. Sorry I can't be more help.

Aw, @ShawnSlavin - you tried. :-)

Beth I've loaded the SU 9 fix for Crystal awhile back when it was the latest. It had the fix in it for the export to Excel issue for an rpt with a subreport in it. I didn't actually test to verify but I read it in their PDF of the list of fixes.

Had a client use SU12 and they had to install Visual Studio first, but it did work out. Both clients are on 2014 PU4 - I thought this would have been fixed but seems like it's reappearing.