DeRay_Scholz
Active Member
Hello all:
I have a situation that I hope someone can help with. Here it goes:
One of our developers has created a new report for label printing. She copied an existing report in CRP, made modifications, tested, checked in.
We then transferred the report to PROD and created new versions and checked in. The problem is this: When we run the report locally, it is looking for the spec files and dll under the CRP pathcode (ie. e:\b7\crpb733\spec\gbltbl.xdb). Since all of our PROD users do not have the CRP pathcode on their machines, the job fails.
Does anyone know where it is pulling this information from?
PS - We also did a test by copying the working report in PROD, completely eliminating any link to CRP, but it still looks for the specs and dlls under the CRP path.
Any thoughts?
Thanks,
DeRay Scholz
The Upper Deck Company
OW B733.2 SP11.1 , WIN2000, SQL2000
I have a situation that I hope someone can help with. Here it goes:
One of our developers has created a new report for label printing. She copied an existing report in CRP, made modifications, tested, checked in.
We then transferred the report to PROD and created new versions and checked in. The problem is this: When we run the report locally, it is looking for the spec files and dll under the CRP pathcode (ie. e:\b7\crpb733\spec\gbltbl.xdb). Since all of our PROD users do not have the CRP pathcode on their machines, the job fails.
Does anyone know where it is pulling this information from?
PS - We also did a test by copying the working report in PROD, completely eliminating any link to CRP, but it still looks for the specs and dlls under the CRP path.
Any thoughts?
Thanks,
DeRay Scholz
The Upper Deck Company
OW B733.2 SP11.1 , WIN2000, SQL2000