2608622 - MS SQL Server Date fields or Stored Procedure Date Parameters, shows as text in Crystal Reports

• MS SQL Server date shows as text field.
• SQL Server date field displays as string data type in Crystal Reports.
• MS SQL Server Stored Procedure Date Parameter, prompt as a String Parameter in Crystal Reports.
• On one computer, the date fields shows as date, but on another computer the date fields shows as string.
• When refreshing a report on one computer, it refresh successfully, but on another one, it generates error in formula because the data type changed from a Date to a String.

• SAP Crystal Reports 2013
• SAP Crystal Reports 2016
• SAP Crystal Reports 2020
                        
• MS SQL Server 2012
• MS SQL Server 2014
• MS SQL Server 2016
• MS SQL Server 2017

1. In Microsoft ODBC Administrator, create an ODBC DSN to a Microsoft SQL Server database.
2. In Crystal Reports, create a report of MS SQL Server using an ODBC connection.
3. Add a date field to the report.
4. Notice the database fields data type displays as date in Crystal Reports.
5. Open the report on another computer in Crystal Reports, and after performing a verify data source, it shows the data type as a string.
          
   Why is this occuring, and how to resolve this issue?

• The data type changes from a Date, to a String, because the ODBC Driver used to connect to MS SQL Server is an old and unsupported ODBC driver, like:
• MS SQL Server (SQLSRV32.DLL); or
• Another older MS SQL Server ODBC driver
           
• When connecting via an ODBC connection, Crystal Reports query the ODBC driver to obtain the data type of the database fields, and some unsupported MS SQL Server ODBC Drivers are returning the incorrect data type: String, instead of a Date. The issue is with the version of the MS SQL Server ODBC Driver, and not with Crystal Reports.

• For MS SQL Server Date Field, or Stored Procedure Date Parameter, to be seen as a Date data type, use a supported ODBC driver for the MS SQL Server version you are connecting to:
          
1. Confirm the supported version of Microsoft SQL Server ODBC driver, for the version of MS SQL Server you want to report from, by looking at the Crystal Reports supported platforms (PAM):
• Crystal Reports 2013
• Crystal Reports 2016
• Crystal Reports 2020
      
2. From the Microsoft website, download the supported MS SQL Server ODBC driver for the version of MS SQL Server you are using.  For convenience, we added the Microsoft website link below:
            
        Microsoft SQL Server ODBC driver download
              
3. Install the MS SQL Server ODBC driver.
         
4. In the Microsoft ODBC Data Source Administrator, create an ODBC DSN using the supported ODBC driver.
     
• For Crystal Reports 2013, 2016:
  Create the ODBC DSN in Microsoft ODBC Data Source Adminstrator (32bit)
    
• For Crystal Reports 2020 :
  Create the ODBC DSN in Microsoft ODBC Data Source Adminstrator (64bit)  
            
• Important Note before creating the ODBC DSN:
• If no other applications are using the ODBC DSN the report use, you can rename or delete the ODBC DSN that uses the incorrect MS SQL Server ODBC driver.
• If there is other application using the ODBC DSN the report use, then create a new ODBC DSN to MS SQL Server, and in Crystal Reports, perform a set data source location for the report, to point the new ODBC DSN

CR, CRDB , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem

SAP Crystal Reports 2013 ; SAP Crystal Reports 2016 ; SAP Crystal Reports 2020