Hi there!

I have a question regarding installation, i have a client/server program where about 40 users using it. i actually installed the main program in the server and just shared the EXE in each workstation.

Will there be a problem in terms of server performance (memory usage, cpu usage, etc.?
or the server works as if the program is installed by each workstation?

Thank you so much!

I am not sure I understand.
You have a network of computer plus a server, and a main program.
What type of program is it (windows, web, database...), that is, what is the resource that the clients are sharing in the server?
What do you mean "shared the exe"? Is the exe copied in each pc? And if yes, does it connect remotely to the server?

Marco

Marco

The scenario is this:
I developed an application using VB6 as front end and MSSQL Server 2000 as my back end. Instead of installing the application in each workstation, what i did was, I Installed the program to the Server and shared the folder containing the application. Then, i made a shortcut to each workstation (client)pointing to the application installed in the server.


so for example, the target of the shorcut icon would be:
\\SERVERNAME\My Application\application.exe

The application is actually running, but what i want to know is, is the approach does'nt effect the server's performance, in terms of memory and cpu usage? or is it much better if i install my application individually to each computer who will use the application?

what would be the disadvantage of just sharing the exe file rather than installing the application to each computer?

Hope it's clear to you...
I hope you can help me..
Thank you!

well.. if you're app is working then you dont have a lot of problems...

but think about net usage.. you are loading a program that is outside the pc you are running it, so every time the app paging itself into memory it will use bandwith to read the next part of the program.
also think about the poor disk trying to serve a lot of pc at the same time...
another think i could think of if where did it save temp files? because if running on the server it will do everything on it..

the app you are describing should be a web app or should be installed on every pc.

besides that, if that work, i dont see any problem with it.

HTH

Gonzalo

I have done this before, what happens is eventhough the exe resides on a server somewhere it will run on the client pc. This means it is using the clients memory, and any reference to App.Path will be to the clients hard drive.

The app will however need to be sent across the network to the requesting client, this could cause issues with bandwidth. You will also need to install any DLLs or OCXs the application uses on each PC that will be using the application. Other than that I found this to be a very convienient way to keep all machines using the application up to date.

Absolutely true!
What you have done is not a client/server application,is just a program that connects remotely to the database in another computer. And that is perfectly fine... To minimize network access, you should try to perform as many operations as possible using the database itself, so the connection to the "client" is limited to only the data that is needed (for example, do a Select with a Where clause instead of getting all records and sort them in the client)
Marco

Thank you so much for your help guys...
Well atleast now i know...

I hope i could you also soon...