Client Server
-
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
-
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
What problem? We have no idea what you have done, what you have tried, or even what you are trying to do!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
Member 14192216 wrote:
Please if anyone has a solution or an idea to solve this problem.
It's very easy. The client app needs to be able to access the server app. Usually you install sql server on a machine and then change the connection string to point to that server. Not to be too critical, but how did you build a POS system without knowing how to change a connection string?
-
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
Exposing an SQL Server directly to the web is a bad idea. You should be putting your SQL Server behind a web service that handles all transactions with the SQL database. Your application on client machines should be interacting with this web service with an authenticated and secured connection (think SSL and HTTPS). It sounds like you have a lot more work to do and your application is indeed NOT finished.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Member 14192216 wrote:
Please if anyone has a solution or an idea to solve this problem.
It's very easy. The client app needs to be able to access the server app. Usually you install sql server on a machine and then change the connection string to point to that server. Not to be too critical, but how did you build a POS system without knowing how to change a connection string?
This connection string can be changed by what? show me please i'm limited by that
-
This connection string can be changed by what? show me please i'm limited by that
Where did you put it? It's either hard coded in your code somewhere or it's in your apps app.config file. It's just text in either case.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
Listen to what Dave said - you need to understand the structure of a distributed (internet) solution. Do NOT expose SQL Server directly to the internet.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
Listen to what Dave said - you need to understand the structure of a distributed (internet) solution. Do NOT expose SQL Server directly to the internet.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
Just thinking that a POS that actually needs a distributed system is also going to need to accept some card payment system anyways. And if the creator doesn't know what connectivity is that means they have not even attempted to put that in play. So this is homework - not real.
-
Good evening everyone, in fact I finished my Point of Sale application on C # .net and SQL server. On the development pc everything is working fine, my concern is to make the application usable in multi-workstation with an Internet connection I have tried everything but to no avail ... Please if anyone has a solution or an idea to solve this problem. Thanks for your help
Your POS talks to the database via a "Protocol" (look it up you need to learn what it means.) There are a couple of ways to do that but the primary one for a distributed system these days for everything is via TCP/IP. That is what you are generically referring to as the "network". You should try to read something, just a little bit, on how TCP/IP works since that is also something you need to know. Your POS is a "client". The SQL Server is a "Server". Those terms are relevant in TCP/IP. There is a "connection string" which is defined in a configuration source, which will almost always be a file. So you need to learn about that "connection string" and how to configure it. To create the correct connection string you will need to know either the "host name" or the "IP Address" (which is something you learn about in TCP/IP) to specify how your "Client" will find the "Server". You can google for examples of SQL Server connection strings and also examples about how you set it up.
