When using Crystal XI, the Access database file (the file generated by the export) is locked and is unable to be updated/overwritten while Crystal XI is still open. Users can attempt the following steps to clear the message:
  1. If anyone has the report open within the Raiser's Edge, Education Edge, or Financial Edge, close the report and then try again.
  2. If the report is open within the Crystal reports program, close the specific report and close the Crystal Reports program and then try again.
  3. If using multiple reports with the same export file (.MDB), make the export file name unique per report (ex: ReportA.rpt uses ExportA.mdb, ReportB.rpt uses ExportB.mdb).
  4. Make sure that you have sufficient rights to the folder where the export database file is being saved.
  5. Locate and delete the associated .LDB file if possible.
  6. Open the report in Crystal. Select Database > Log On or Off Server > Current Connections. Select the .MDB file and click Log Off.
  7. If using Crystal XI and Windows 7, open the Task Manager. Select the Processes tab and end the process of any "crw32.exe" instances. .
  8. Recreate the .rpt file
Note:  We have seen this issue occur within Raiser's Edge>Reports>Custom Reports if the crystal report has subreports and is using shared variables.  The following workarounds may resolve this issue.  Only one of the below workarounds is required.
  • Workaround 1:
  1. Open Crystal report.
  2. Create a new shared variable formula.  This shared variable can be any of any type and can be given any name.
  3. Place this new shared variable formula in the main report section(s) where the subrepor(s) that use shared variables are located.
  4. Suppress these new shared variable formulas.
  5. Save report and close out of Crystal.
  • Workaround 2:
  1. Open Crystal report.
  2. Select File>Report Options.
  3. Check the 'Save Data with Report' option.
  4. Save report and close out of Crystal.

Blackbaud has reviewed the message and determined this is not a defect in the software and will not be addressed in the program in its current state. Implementing code changes to remove this message may introduce high risk behavior that outweigh the potential benefit of resolving this message.