TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
msnelling
NA
4
0
Dynamic connection string
Dec 28 2003 11:26 AM
Sorry about being unclear. I am new to .NET and I am unsure of how to go about this program. The questions I am asking are very broad because I don’t know where to start. I can refine them as the conversation progresses. I have no set parameters for this program. I want to end up with a small program that can be distributed to companies and easily installed. I assume MSDE would be the best to thing to use considering the target users. Project: 8-10 forms each with 1 or more data grids This will NOT be deployed to the net. It is a stand alone program that requires a database to store data. The database must be with the program. Database: MSDE Total size will never exceed 1 Gig (I am assuming this is the DB of choice in this situation) Target users: The program will be distributed to a variety of small businesses who are all windows users. These businesses are not connected to each other by a network and are unrelated to each other. Goal: To create a small program that I could distribute to these companies. It will be self contained in that it will come with the program and the database in one package. I would like one connection string available to the whole application. Questions: Is it difficult/possible to make the program so it can be installed on either a network or on a single machine? If it is difficult…forget the network stuff for now. As for the questions concerning when I want to supply the db name and such. I have no clue, nor do I have any preferences. What is the easiest and most efficient way to do it? If possible I would like to end up with a connection module that I can reuse. You would think something so basic would be a bit more stratigh forward.
Reply
Answers (
2
)
iCodeLibrary.NET goes open source
Building Office add-ins in C#