Eliminate hardcoding of connection string

Question

0.00/5 (No votes)

See more:

I have made GUI that can perform usual operations with the database ( load existing data, modify it or add new entries). GUI is made in C++ using raw WinAPI.

The problem is in connection string. It is hardcoded so it forces the user to keep the database in the same folder where the GUI is.
Below is the example in C++, using ADO:

C++

static wchar_t *bstrConnect= L"Provider=Microsoft.ACE.OLEDB.12.0;\
                                 Data Source = .\\MyDatabase.accdb";

I wish to allow user to have freedom of choice when it comes to where database will be located but I do not know how to modify the application/connection string to do this.

I have tried to search here for examples, and have searched online but had no success. Perhaps me being a beginner and self-taught has something to do with that.

QUESTION:

Is there an example/tutorial/documentation that can show me the correct principle for handling this type of "scenario"?

Posted 23-Jan-15 6:03am

AlwaysLearningNewStuff

Add a Solution

Comments

ZurdoDev 23-Jan-15 12:30pm

Just store it in a text file then. You can even encrypt the value if needed.

KarstenK 23-Jan-15 12:38pm

Or in the registry. Think also about security. The password should be encrypted, or best NEVER stored but every program launch be asked. (with user name)

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2015-01-23T06:58:00

Not sure if I understood your question correctly, but why not store the database location in a simple configuration (text) file in the same folder where the application is.

The first time the application runs, let the user specify the database location with a File Open dialog and store the location in the configuration file. Personally I wouldn't store the whole connection string in this case, just the location and then build the connection string in the program.

What comes to security I'd use a database password for the database and when the database is opened I'd ask the user for the password. I wouldn't store the database password anywhere.

About database password, see Set Database Password and Unset Database Password[^]