Path to Access Database
-
I want to store the path of an Access database that will be used during my application. When the application loads, it can check the path stored in a file of my choosing and determine whether or not the file is still in the same location. How would you suggest I store the path? A text file seems the simplest way to go, but would provide little or no security. Any suggestions would be appreciated. Thanks.
-
I want to store the path of an Access database that will be used during my application. When the application loads, it can check the path stored in a file of my choosing and determine whether or not the file is still in the same location. How would you suggest I store the path? A text file seems the simplest way to go, but would provide little or no security. Any suggestions would be appreciated. Thanks.
is this file path relative to the application being built? or is it static to each client the app will run on? If the concern is someone coming across the file path storage device(ie textfile) you could try storing it encrypted then comparing the encyrpted file path or if its just a concern of someone coming across it and modifying it by 'accident' you could store it in isolated storage...it would be harder for them to find it. there...you could also encyrpt it then as well. - string Beautiful; Beautiful = "ignorant"; label1.Text = "The world is full of " + Beautiful +" people."; Why is common sense such an un-common comodity?
-
is this file path relative to the application being built? or is it static to each client the app will run on? If the concern is someone coming across the file path storage device(ie textfile) you could try storing it encrypted then comparing the encyrpted file path or if its just a concern of someone coming across it and modifying it by 'accident' you could store it in isolated storage...it would be harder for them to find it. there...you could also encyrpt it then as well. - string Beautiful; Beautiful = "ignorant"; label1.Text = "The world is full of " + Beautiful +" people."; Why is common sense such an un-common comodity?
The Access database itself will be in a location of the customer's choosing, probably on a server, while the the file holding the path will be relative to the application. I was just concerned about somebody who shouldn't know discovering the location of the database. It's probably not a huge concern because I'll put whatever security measures I can in place to protect the database itself. If they tinkered with the file holding the path, the application will simply not run (or not run correctly). I also plan to allow an authorized user to reset the path to the database (through an application form) should anything change (the location of the database, the file holding the path, etc). Anyway, thanks. I'll try storing the data encrypted.
-
The Access database itself will be in a location of the customer's choosing, probably on a server, while the the file holding the path will be relative to the application. I was just concerned about somebody who shouldn't know discovering the location of the database. It's probably not a huge concern because I'll put whatever security measures I can in place to protect the database itself. If they tinkered with the file holding the path, the application will simply not run (or not run correctly). I also plan to allow an authorized user to reset the path to the database (through an application form) should anything change (the location of the database, the file holding the path, etc). Anyway, thanks. I'll try storing the data encrypted.
Try storing it in iso-storage(isolated) in encrypted form, and then pwd protect the access db...thats the best way i know to keep access safe on someone else's system. string Beautiful; Beautiful = "ignorant"; label1.Text = "The world is full of " + Beautiful +" people."; Why is common sense such an un-common comodity?