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?