Joined: 06 Oct 2009
Online Status: Offline
Posts: 39
Topic: database location Posted: 08 Aug 2013 at 11:19am
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?
Joined: 21 Dec 2007
Online Status: Offline
Posts: 4372
Posted: 09 Aug 2013 at 4:42am
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.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum
IP Logged
