Samuel - you are right. I know this problem. When we change the reports to load from different DB; initial load is around 2 mins. I tried removing the connection info from CR but it always expects atleast one connection info embedded in .rpt file. I found alternate solution. Having a util which will load all the reports; set the new connection info and save the report files. This util can be part of some overnight job process during initial setup of an app.
On Friday, November 11, 2011 5:38:49 PM UTC+5:30, samuel mathew wrote: > Here is the problem: > Crystal Reports saves the design time database connection info in the > rpt. When our application tries to run a report against a production > database, the rpt takes a long time (60 sec.) to load. After it has > loaded we can change the database logon (in our code) and the report > runs successfully. > It seems like Crystal is trying to connect to the development DB > server (but it cannot see it from the production environment). If we > edit the rpt and save the production database connection info in it, > the report loads in less than a second. > We are an ISV and our application is used at over 2000 sights so it > is > not practical to edit each rpt (we have over 850) at each location. > Is there some way to tell Crystal not to try connecting to the DB > during the report.load? -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to dotnetdevelopment@googlegroups.com To unsubscribe from this group, send email to dotnetdevelopment+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
