This is regarding general protection of a database hosted on a network. I am
developing a database application for my college library using VB.NET, that
will reside on a network.
For some reasons, I did not want to hardcode the Database location in the
application. Instead, when a user logs in, he can choose the database
location using a folder browser control, if the location has changed.

Now, I realize that for this, I have to put the database in a shared folder,
which makes it quite vulnerable. Having pondered over the problem for
sometime, a solution that comes to my mind is to place a Text file in the
same shared folder that always contains the correct path of the database.
When a user chooses that folder, I will read the actual path of the database
from the text file, and move the database to a non-shared folder.
I haven't yet implemented this approach, but felt it better to consult
someone before. So, would this approach work, and is it a good idea.