Board index » Visual Studio » Run VB6 .exe on server from a remote machine on same network; db is SQL Server 2000

Visual Studio164
Hello --



Please advise if there is a more appropriate group for this post.



I don't have the networking skills to solve this problem, and need some

help.



The exe and the SQL Server 2000 db are both located on the server (Win 2003

Server).



What do I have to do to be able to run the app from another machine on the

network?



Thanks for any help.



Larry Mehl


-

Do you mean to run a program from a remote server on a local PC, or run a

program on a remote PC and control it locally?



For the first option you must install all the runtimes and the SQLServer

client on the local machine, as you do that you might as well install the

program at the same time and avoid the network traffic of running a program

across the network. Don't imagine that by having the program and the

database on the same server you will reduce traffic, in fact it will be

worse as all the work is performed on the local PC while all the data is

remote.



For the second option any remote operation software will do the job,

PCAnywhere, Remote Desktop, Citrix (overkill perhaps).



Best Regards

Dave O.



"L Mehl" <mehl@cyvest.com>wrote in message



-

Dave --



Thank you for the suggestion.



Ours is the first scenario: Running the app (residing on a remote server)

on a local PC.



When you say "might as well install the program (on the local PC) at the

same time", do you mean that we do not have to also install all the runtimes

on the local PC?

If "Yes" then I assume we can delete the app from the server. Am I correct?



When you say "SQLServer client on the local machine" do you mean MSDE? Can

you explain the purpose for that? The app contains a connection to the db

using a DSN.



Larry







"Dave" <nobody@nowhere.com>wrote in message



-

Yes you need all the runtimes on the machine which is running the program.



If you have a connection by DSM you already have all the components needed,

different operating systems come with differing levels of support for

databases loaded by default.



There are very many ways of connecting to a database in Windows, if what you

are using works then go with it. The SQLServer client loads some tools for

manipulation of the database - I can't remember of the top of my head as

they are not installed on the PC I'm using now.



Best Regards

Dave O.



"L Mehl" <mehl@cyvest.com>wrote in message



-

Dave --



Thanks again. I appreciate your continued help.



By "runtimes", do you mean the dlls, etc., that the app needs in order to

run?

e.g.,

msado25.tlb

msdatsrc.tlb

dao360.dll

MSBIND.DLL

MSDERUN.DLL

MSSTDFMT.DLL

COMDLG32.OCX

DBGRID32.OCX

MSADODC.OCX

MSDATGRD.OCX

MSDATLST.OCX

MSHFLXGD.OCX



We used InnoSetup to build the installation script. The script included the

above files.



If the connection to the db is a DSN, why is the SQLServer client needed on

the user's machine.



Larry





"Dave" <nobody@nowhere.com>wrote in message



-

"L Mehl" <mehl@cyvest.com>wrote in message

Yes, that lot should do the job



It's not, I said "If you have a connection by DSM you already have all the

components needed"



Best Regards

Dave O.





-