Hi, I don't think it has anything to do with the db.
The first time you load any report, it will take a minute or more. After that they will load in an instant. What I do is in form load or some init, load any empty or small .rpt with a background worker. You don't need to display it or anything. What happens is you are still taking the "first load hit" but you won't ever notice it and ALL reports will seem to load in an instant. This is a known problem with CR as they load a huge amount of thing when first started. You will be good to go as long as the app runs. Give it a try. Mike On Nov 11, 7:08 am, samuel mathew <byju...@gmail.com> 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
