how to create Multiuser software

Question

0.00/5 (No votes)

See more:

Dear all,

I want to create a multiuser software.
Presently I m using sql database and vs2008.
I m creating a client side software.
Is it run on the network or not ?
Is It run on multiuser Platform or not? (Like one user use the database and then next user used the same database.)

Please tell me it is the right way or wrong way and tell me how can be it’s possible.

database can be put on the external harddisk when the sql server running.

Posted 3-Sep-13 4:12am

Manish Arya

Updated 3-Sep-13 4:16am

v2

Add a Solution

Comments

[no name] 3-Sep-13 10:23am

"Is it run on the network or not ?", sure if you want it to.
"multiuser Platform or not", what is that you think a "multiuser platform is"?
"Like one user use the database and then next user used the same database.", if you use the same connection string to the same database, what do you think the problem is?

2 solutions

Solution 1

Generally when you break up your application into clients and a database server then your application is multiuser (there are specific things you should do but for your purposes you can ignore them).

If you connect to that database server from different clients then you are multiuser (database connection strings www.connectionstrings.com.

Right and wrong depends on many factors which you can ignore if your application works.

It is unadvised to put your database files on external hard disk drives (the USB kind).

Posted 3-Sep-13 4:30am

Mehdi Gholam

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)

Bala Selvanayagam · Accepted Answer · 2013-09-03T04:36:00

Solution 2

Hi,

As far as your client side programme is separate from the database and you use a connection string to point the SQL server database, it will work on the netwok and yes you can make it multiuser (you have to handle the users)

There users will be accessing the database via the client program and its not correct to think that a database is for one user.

yes database files can be put on the external hard disk but i would not advice.

If you could explain more your situation and what you are trying to do including the programming languages you are then will be able to comment specific

Posted 3-Sep-13 4:36am

Bala Selvanayagam

Updated 3-Sep-13 4:40am

v2

Comments

Manish Arya 3-Sep-13 11:44am

Dear Sir,yes i m using connection string. i m using the c# language.

i want to tell you what m i doing in this prject.

i m creating some window form and a parent form and connect through the connection string and its working fine in my single system. i want to know about this program could be run or not on the network when i m installed the client software in the first computer and database installed in the second system.

if it is not worked then how can be set the network property.

Bala Selvanayagam 3-Sep-13 11:57am

Hi Manish,

Understand, yes this will work on the network environment - means will work on the Local Area Network (LAN) but may not be on the (Wide Area Network) WAN. Do not define the connection string in many places with in your program and this is a bad practice.

Try and keep the connection string in a single place so that you can edit easily.

I would recommand you to do your first form and create a installer (when you double click) it installs and then try out from two workstations pointing to the same SQL database. This will give you an understanding of how the architecture is going to be