The Crystal.Net API reads all sections of the reports and objects within the section and creates the object tree. When processing a Quick Report or Info Service report request the IFS Crystal Web Service will first try to read and load the layout in to a Crystal Document object in memory using the Crystal.Net APIs. The issue drills down in to two ways where this performance issue can occur and is related to the 3rd party Crystal.Net API used by the IFS Crystal Web Service framework. It’s also seen that it takes a long time for the IFS Quick Report Parameter Dialog to show the Quick Report Parameters. It will take a long time to process when previewing an Info Service or a Quick Report of type Crystal. Why does it takes a long time to process or execute a Crystal Report at runtime? ¶
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |