SOLUTION #1

Test and validate the ODBC connection through the ODBC Data Source Administrator. The steps below will change the Data Source authentication from a SQL login to Windows Authentication (recommended):

  1. Open the ODBC Database Administrator(32-bit systems: Start, run: odbcad32 64-bit systems: Start, run: %windir%\SysWOW64\odbcad32.exe).
  2. Select the System DSN tab.
  3. Select the appropriate ODBC Data Source* and click Configure (ex: RE7_1, RE7_Sample, or REINI_1, REINI_50 or AFNINI_1, AFNIN_50).
  4. Verify that the SQL Server name and Instance name is correct (ex: SQLSERVER\SQL2008).
  5. Click Next and select With Windows NT authentication using the network login ID.
  6. Click Next, make sure the database name is in the drop down list and then click Next, then Finish.
  7. Click Test Data Source, it should say TESTS COMPLETED SUCCESSFULLY!
  8. Click OK 3 times exit the ODBC.

*If there are no ODBC Data Sources listed in the System DSN, you're most likely on a 64-bit OS and will need to run %windir%\SysWOW64\odbcad32.exe instead.

SOLUTION #2


If the report runs successfully in the Crystal Reports stand alone application but generates the error only in the plugin section of the Blackbaud application:

  1. Open the report in the Crystal Reports application
  2. Make note of all the subreport names contained in the main report (if there are more than one subreports, also note the sequence in the report)
  3. Open the plugin database file (ex: ReWrap.mdb) in Microsoft Access and edit the Subreports table
  4. Insert the exact names of all the subreports noted in step #2
  5. Enter consecutive sequence numbers (from step #2) if there are more than one subreports in the main report, else enter 1.
  6. Save the database file