x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 7 replies
  • Subscribers 121 subscribers
  • Views 3890 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
BobLoblaw2

Crystal Reports Quotes Appear in Export

Posted By

We export a bunch of reports in CSV format using Crystal Reports. I just updated to Sage 100 2016 from MAS 200 4.4 and something weird is going on.

When we try and export a report to CSV format on the Server/Remote Desktop, the Delimiter and Separator fields are empty for the Separated Values Export Option Window. On a workstation, quotes are defaulted in the Delimiter and a comma for the Separator.

The specific report we need wants the Delimiter blank, and deleting the quotes on the workstation so the Delimiter is blank actually makes the report work fine. With the Delimiter blank on the Server though, the quotes are actually exported in the report.

I noticed there is a service pack available for Crystal Reports 2011. Is it safe to update install the service pack?

Thanks!

  • 0
    Can you export to Excel (workbook data only). Open the file and then save it as a CSV file?
  • 0 in reply to BShockley
    We upgraded from 2015 to 2017 and have a very simple custom crystal report on the AP custom menu we used to always export to a .csv file. It's only 3 columns no headers or footers and when we export it now all data comes over to excel into one column (col A) instead of 3 columns (A,B,C). The only way to work around this is to put a comma in the export options Separator box. It's an extra step that users have a hard time remembering. What changed in 2017 that causes this?
  • 0 in reply to dhalpin
    Hi, The issue is due to an upgraded Crystal Reports runtime engine. You can download a newer version of the engine that will resolve the export issue. The update will need to be installed on all workstations and the server. This is planned for an upcoming Product Update.

    The fix is to update the Crystal Run Time components Support Pack 18.

    From SAP Crystal Site:
    blogs.sap.com/.../

    Make sure to download Support Pack 18 “32bit.msi”

    Extract the files then ‘install’

    John Nichols
    Sage
  • 0 in reply to jcnichols
    Thank you this worked perfect! Our workstations though do not have crystal reports 2011 installed for sage 100 because they have an older version of crystal that they use with another program and the 2011 install would interfere. Do you know if this support pack would interfere with their other version of crystal or is this just updating sage 100 crystal run time components?
  • 0 in reply to dhalpin
    HI, The Sage 100 workstation installs the crystal run time components, even without the Crystal Designer. (all framework reporting uses the Crystal run time components) without knowing what version the older Crystal is or the application that utilizes it I can't comment on the compatibility. Thx
    John Nichols
    Sage
  • 0 in reply to jcnichols
    Thanks for the info John.

    I tried this and now instead of the field being empty, it says 'DEFAULT_NULL' instead. I tested this on the server itself and not on any of the workstations.

    Brent
  • 0 in reply to BobLoblaw2
    Hi Brent, That is the issue (DEFAULT_NULL), in the run time shipped with 2017 the values are blank meaning the export has no delimiter or separator. Unless you are running the export on the server you will need to update the workstation. Thx John

*Community Hub is the new name for Sage City