CE90WIN_EN_SP5

CE90WIN_EN_SP4
Object management
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.
Object model
ADAPT00266463
Description:
Patch ID: 36680795
Sorting is ignored when it is applied through a recordset. The records in the report are shown in the original order, rather than being
sorted.
New Behavior:
This problem is resolved.
ADAPT00341749
Description:
Patch ID: 36674102
When connecting to a CDO recordset at run-time, Crystal Reports generates an error because the QueryEngine incorrectly interprets
field names that end with a bracket pair containing a number. For example, (1), (2), (3), and so on.
New Behavior:
This problem is resolved.
ADAPT00345803
Description:
Patch ID: 37021362
Any application that has been created in Visual Basic 6, uses the Report Designer Component, and then connects to the disconnected
recordsets, will create a memory leak. Eventually, the system crashes.
New Behavior:
This problem is resolved.
The problem stemmed from a Rowset that holds on to another Rowset when data is fetched.
Path Mapping