|
When starting a .net solution, the database is normally located in the bin\debug directory. However, when deploying the project, the database is in application startup path which forces this user to make the change in the report.
Is there a better way to make the location of the db?
Thank you.
|
|
The simplest solution in my mind is to not have the report 'pull' the data from the database at all.
Have you application gather the data and 'push' it to the report via a ADO.Net(XML) connection for the report.
Now the location of the database as far as reporting goes is irrelevant, the report gets the data and displays it.
The problem becomes parameters, which I got around using my parameter input form (which also allows much better control over the selection and display of parameters)
Yes, it is probably more work than you wanted, and so may not be the solution that you use, but it is one way around your issue.
The other thought is to create the db in a set location like: c:\program files\your app\db or any other location.
HTH
|
IP Logged
