YES, its true
Because the report what you create before, say SQL SERVER "SQLSVR1", and when
you move the report to the different location say SQL SERVER "SQLSVR2", here
the server is diff and may be the login may remain same.
Fos such situations you have to change the location of the report object ar the
runtime depending on the SQL Server where you execute them.
USE
ConnectionInfo();
TableLogOnInfo();
rd.SetDatabaseLogon(DBUserName, DBUserPassword, DBServerName, DBName);
these are the methods to change the location of the report at the runtime
and you never get that box.
FOR Ex:--
I have report uses SP to get the data from 7 diff tables, So i have created this
report with our SQL server "SERVER1". Now report is fine executes and even it
shows the data properly for the given output.
Now I have the situation to take this report to some other machine or to clients
machine in diff location. WHat i have done is that, I have the keys in the web.config which are "DBUserName, DBUserPassword, DBServerName, DBName".
When I deploy the report at other machine, i change the key value as needed to
the current envr. and change the location of the ReportObject (SP or TBL)
telling it to take from the new database location.
By doing this that "BOX" is avoided and we need not to change/modify the report
again in the other machine. All is dynamically changed while the time of
executing.
If you have done this for windows application then put those keys in app.config
file.
Hope this helps
With Regards,
Raghavendra Mudugal
|