September 10, 2006 at 7:47 am
Hi. I have an application developed in .NET that works fine in a PC.
Now I want to run it from other PC's in the LAN.
Which considerations should I take into account?
I assume I have to install SQL SERVER client tools in the other PC's. Right?
Anything else?
September 10, 2006 at 9:55 am
If its a web based application you don't have to install anything. If its a client server app then u need to install obdc(connectivity). You don't have to install SQL Client.
Hope this helps
Thanks
Sreejith
September 10, 2006 at 2:07 pm
Thanks for your answer. It is not a web based app. nor is it programmed to act as a client/server.
I just pretend that a user in a LAN can query/update the data base.
Thanks for your help
September 11, 2006 at 12:17 am
Hi
You probably are not using ODBC to connect to SQL using .Net...So all you would need to do is ensure your client PC has the .Net Framework installed...And in theory if you are not using any external DLL's you can just copy your exe to the machine and it should work....Should you want to distribute your application to other clients it would be best to build a setup package you could add the framework to this setup to ensure it is installed.
Mike
September 11, 2006 at 6:54 am
Based on your statements "nor is it programmed to act as a client/server" and "I just pretend that a user in a LAN can query/update the data base", you might have connection issues with the app on another PC. For example, if your connection uses "(local)" as the server name, the app on a 2nd PC is going to look for the DB on that PC, not the original PC. If you're installing an app on multiple PCs with a single database that all of then work on, you do have a "client/server" setup, whether your DB is on a true "server" or just a PC acting like a server.
September 11, 2006 at 7:14 am
OK. I understand this. Now, what should I do for it to work?
How do I "install ODBC connectivity?
September 11, 2006 at 7:26 am
It depends on exactly how you're making your SQL connection. Typically you'll have a SqlClient.SqlConnection object and you'll be setting the ConnectionString property (review the subject "connection strings" beneath the "SqlConnection class" entry in MSDN). A simple connection string could be "server=(local);database=MYDB;Integrated Security=SSPI". This will connect the app to the MYDB database on the local machine using Windows authentication. If you used this string in an app running on a second machine, it would also look for the DB on the local machine. Simplest fix would be to hard-code the actual PC name where the SQL database will be. For example, if you have PCs named "Computer-A" and "Computer-B" and SQL is on A, change the conn string to "server=Computer-A;..." However, if you ever change the location of the DB you'll have to fix the code, recompile and redistribute the app. I always use a registry setting (updated thru a form in the app) for my DB conn string settings. That way if the server changes, the conn data can be easily updated without a lot of pain.
September 11, 2006 at 9:10 am
Pls forgive my ignorance. There are some terms that I do not understand.
"Typically you'll have a SqlClient.SqlConnection object": where?
"SqlConnection class" entry in MSDN: what is MSDN?
And, all this has to be done in the client? or the server?
Do I have to install SQL in the client?
I tried to go thru the Ad Tools of windows, add an ODBC Source for SQL using pipes (TCPIP did not work in the client although it did in the server) and the connection went thru.
September 11, 2006 at 9:26 am
Maybe it's best for you to define exactly what you mean by "I have an application developed in .NET". Did you develop this app? If so, please explain how your .NET software is working with the SQL database.
September 11, 2006 at 1:20 pm
I use Genexus, a high level tool for developing applications.
At this time I really think that this has to be solved within the Genexus world.
Many thanks for your attention. I'll let you know what it was.
best regards
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply