Service Pack Readme (Adapt)

CE10WIN_EN_SP3
Object management
ADAPT00116785
Description:
Patch ID: 36819203
For scheduled reports which have parameters with default values, the descriptions for the default values are not displayed in the schedule history,
both in the Crystal Management Console and in Crystal Enterprise.
New Behavior:
Parameter default value descriptions are now displayed in the schedule history.
ADAPT00190903
Description:
Patch ID: 37167226
When objects are deleted from the Crystal Management Console (CMC), the deleted objects still appear in the repository folders.
New Behavior:
The Crystal Input File Repository Server and Crystal Output File Repository Server deletes objects to accurately indicate when objects have been
deleted from the folder structure.
To enable this behavior, users must disable the Job Server and add the command [-prune] to the command line of the Repository Server (Input or
Output) that is set to delete the empty folders, and then restart the server. The server shuts down automatically when the empty folders are
deleted. You can add [-trace] to obtain a log file for the number of folders visited and the number of objects deleted. Remove [-prune –trace]
once the files are deleted.
Known Limitations:
If a user deletes all report instances from the CMC, the system deletes the following folder: "Install Directory\FileStore\Output." If a user deletes
all objects from the CMC, the system deletes the following folder: "Install Directory\FileStore\Input." If either of those folders is deleted, the file
repository servers are inoperable because the root folder ("Input" or "Output") is absent. To start the servers, users must recreate Input/Output
folders.
ADAPT00353037
Description:
Patch ID: 36750290
Importing Segate Info 2.5 recurring instances scheduled to Microsot Excel format into Crystal Enterprise 10 causes the output file to become the
Crystal Reports .rpt format instead of the Microsoft Excell .xls format.
New Behavior:
This problem has been resolved.
Object model
ADAPT00208927
Description:
Patch ID: 36998113
In a Microsoft Visual Basic 6 application, an exception error occurs when users pass an RDO recordset to a report.
New Behavior:
This problem is resolved.
The ODBC driver has been modified to accept RDO recordsets. Only the rdUseClientBatch cursor driver is supported. For example:
myRDOConnection.CursorDriver = rdUseClientBatch