Parameters not being passed CrystalReport ver 6

[Guest_imported]

Everything was working perfectly. Then we had to update our ODBC source because the logon id and passwords were changed. We changed all the locations (set location) and verified database for all the reports. We refreshed the reports and now the reports are not working properly. Can parameters disappear when a refresh is done?

I'm at a complete loss. I have tried just about everything but redoing the reports. What happens to these reports, it shouldn't be so difficult to change ODBC source and do a refresh. Is there something missing here?

 

[kenhamady]

Changing ODBC in itself shouldn't cause problems, unless they affect things like data types or joins (which is possible)

What isn't working?
Is there an error message? Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal

 

[Guest_imported]

It appears that the parameters are not being passed to the reports from the ASP pages. For example: We have a CV report. The user should be able to choose an employee and that employees CV should appear. When we did a refresh on the report after changing the ODBC, the parameter field disappeared so we got CV for all employees. The we inserted a parameter and it appears like the report just hangs itself.

The old report had the rights of an administrator (ex: "sa" in the database, now it's changed.)

I appreciate any help I could get.

 

[ferreras]

Yes, I'm having the same problem!! If anyone could help "us", we thank you a lot!

 

[kenhamady]

Troubleshooting questions:

Does the new user name and password have access to everything needed by the report?

Did the set location/verify pick up any changes in the tables?

After you changed the ODBC and verified it does the report still run OK in the design environment?

Did the report (that is in the design environment) lose the parameter completely when you changed the ODBC or did the ASP simply not prompt the parameter that still exists in the report?

Did you update the login in the ASP code?

Is the parameter a Crystal parameter or is it coming from a stored procedure?

Can you create a new simple report as a test to confirm that the new ODBC setup doesn't have an inherent problem when launched from ASP? Ken Hamady

http://www.kenhamady.com/

Crystal Reports Training and a
Quick Reference Guide to VB/Crystal