Application Issue with Access and ReportViewer
-
I'm writing a small application at work (programming isn't my primary job function at the moment). I'm using Access to keep track of some information...it's mostly static. At the moment the application and the access database reside on a network share because a few people in my department need to access it. However, I'm using ReportViewer in Visual Studio 2008 and the ReportViewer dlls aren't installed on any of our office machines. If I stick the dlls on the network share they're aren't recognized. I don't have administrative rights to install them on each machine. My thoughts are to zip on up the application and put it on each machine with the dlls files included. However, the access database needs to remain on the network share so that each user only accesses the one copy of the database. I'm planning on leaving the company in a couple months and no one in my department knows C#. If the network share's URI changes in the future, the application will break. Are they any suggestions for a way to have users be able to change the URI within the application and if it use that URI in the future if for some reason it changed? I want to make it as easy as possible for some of the folks here. I'd rather not have to come back and fix the application in the future just because they decide they need to restructure every year.