We have some technical question about Crystal Report .NET, which is very important for us. Hope you are able to answer our questions as soon as possible… For years we have been using RDC (Crystal Report Designer Component) in our classic asp web solution. It has been working for years, but is now a product that you don’t support anymore. Over the past few years we have converted many parts of our solution to ASP.NET, and that is also the way we are going in the future. So soon we will have no more classic asp pages in our solution. Recently we have implemented SAP Crystal Report .NET, which is intended to replace the older technology : RDC (Crystal Report Designer Component). Link to runtime package for SAP Crystal Report .NET : http://scn.sap.com/docs/DOC-7824 After a week testing at 2 of our customers, we have ran into problems. Unfortunality SAP Crystal Report .NET has some serious limitations. Apparently Crystal Report .NET has the limitation of 3 CPL (Concurrent Processor Licensed) at a time, the rest are queued. Also the maximum of 75 print jobs. (according to the following answer from one of your employee, : http://scn.sap.com/thread/3498022 ) Is there any way to avoid the limitation of 3 concurrent processes? RDC has been working fine at many of our customers, but we can’t find that there are any such limitations or are there the same limitations in RDC? Is SAP Crystal Report .NET even slower and less scalable than the older technology RDC (Crystal Report Designer Component) ? What are our options of scalability for a solution in ASP.NET, because some of our customers with own servers have many users? We found a post on a newsgroup that suggest Crystal Report Server. Is that the same code as SAP Crystal Report .NET? or is it completely different? Sincerely
↧
