Broken Parameter in Crystal Reports - fatal corruption

Post Author: pontupo

CA Forum: Data Connectivity and SQL

Put this under Data Connectivity since it's partially related to that (more so than anything else, at any rate). I recently managed to completely corrupt a report document through a series of steps that was something like the following:1) Create a report linked to a given data source.2) Create a parameter field and link it to an aspect of that data source. I think, though I'm not sure, that my parameter was a dynamic field linked to some set of values in my data source.3) Change your data source via Set Datasource Location. You may be given some sort of warning, but you can disregard it. Clearly I shouldn't have disregarded it...At this point, you will have an orphaned parameter field that exhibits some odd behavior. First off, you can not delete it (which is the worst of it), nor can you edit it. The only way in which you can modify the parameter is to rename it (which isn't very helpful).You won't be able to modify the values assigned to any parameter and attempting to do so will crash Crystal. The Dependency Checker will flag the parameter, but won't give you any useful indication of how to get rid of it. Basically, in order to utilize the report at all (if you want to use parameters, anyway) you will have to rebuild it from scratch, which is to say that you can't utilize it at all. I've found very little mention of this online and thus have no solution, so I figured I'd ask here if anyone has any brilliant ideas. My only consolation at the moment is that at least I can open the report so that recreating it won't take as long as the original construction... but that's some small consolation as this was numerous days of work T_T Pont