SUBREPORTS DO NOT WORK WHEN CHANGING DATABASE

[gruiz1998]

Hi everyone!

I have a main report and 2 subreports linked to it (the client was made with VB6, DB is SQL server, Crystal reports version is 8.5 ), both of them use parameters from the main report and everything works fine with our development DB, but changing to the production DB the report does not work anymore unless subreports are taken away, Does anybody has had a problem like this?

Thanks in advance!!!!!!

 

[kskid]

Whenever I change databases, there;s two things I always do.

1. Database->Set datasource location (or is it change datasource location. I'm at home so I trying to remember)
2. Database->Verify Database

-LW

 

[gruiz1998]

Thanks a lot kskid for your suggestion, however let me tell you the program in VB checks the registry (wich is the place where is directed to ) in order to find the path, user and pwd to access the DB, and in Crytal Reports I use "Verify database" to ensure the report is conected to the right database and still does not work.

Do you have any other idea?

 

[MJRBIM]

In CR you need to set the data connection using the SET LOCATION function for all three reports (1 - main report, 2 - subrpeorts).

You're probably only updating the DB info in the main report.

 

[synapsevampire]

Verify database should be checking the subreports as well, however if you are using VB and storing connectivity within the registry, then it sounds like a VB issue.

Not sure why you elected to store and retrieve the information within the registry, it isn't required as Crystal will retain connectivity within the report. If you are going to store the connectivity, you'll need to do so for the subreports as well.

-k

 

[gruiz1998]

Thank you both, MJRBIM and synapsevampire, I missed "Set Location" also SQL permissions were affecting the whole conectivity.

Now all reports are working!!!

Thanks a lot!!!!!