You can launch SAP Crystal reports and dashboards directly from SAP Business One. SAP Crystal Reports, version for the SAP Business One application allows users of SAP Business One to create pixel-perfect reports and dashboards by connecting exclusively the SAP Business One data model with the SAP Crystal Reports environment.SAP Crystal Reports Viewer is a free desktop application (Windows or Mac) allowing recipients of SAP Crystal Reports files (.rpt file extension) to open the document and interact with the data saved within the file, including search, drill-down, print and export – but not refresh (which require SAP Crystal Reports).NET and Java to embed reporting capabilities into their own applications. SAP Crystal Reports for Visual Studio (using.NET) and SAP Crystal Reports for Eclipse (using JAVA) are free add-ons for developers using.You can as well access reports by using a browser or a mobile app. With SAP Crystal Server 2020 5 CAL, you can automatically distribute reports customized for individual recipients. With SAP Crystal Server 1 NUL, you can schedule reports to be pushed out to recipients as PDF email attachments, access the reports securely, and refresh the data by entering various parameters. SAP Crystal Server provides a platform environment through which you can share documents (such as SAP Crystal Reports files) with end users.SAP Crystal Reports allows a report designer to include data from various sources to create a document on his/her desktop computer where the data is formatted into a design of their choosing, such as an invoice, a sales or operational report, a marketing letter or some sort of analytic visualization.This file can be moved from computer to computer fairly easily.Īnother option is to create an 'install' to create the DSN on other computers, but you have stated that you do wish to do this. If you use the DSN, the connection string will basically be placed in a text file for the application to use. The MSDN library has plenty of information. You can create a file DSN on anycomputer and then dump it into the application install path and use 'DSN = app.path & '' in your connection string.
The file DSN may even be easier, although it further abstracts the connection string by placing it in a file and forcing the app to use the OLEDB ODBC provider (adding an extra layer) instead of just the OLEDB provider for SQL Server. Provider=SQOLEDB.1 Server=atabase= UID=UserID PWD=Password You would be better to recode the connection string to the SQL Server database as a connection string, not a DSN.