Re: Who is using the EXE
- From: "Dave O." <nobody@xxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 13:20:54 -0000
Running applications across a network is a bad idea for several reasons, the
locked file is just one of them.
The normal solution is to write a small launcher program which is installed
to each users PC. When the launcher is run it looks at the executable on the
server and compares its version number with the local copy of the same
program, if it finds a newer one on the server it copies it over the local
copy and finally it runs the local copy of the program.
This automatically updates the local file and ensures the copy on the server
is never locked and reduced network traffic by not having to access the
executable over the network all the time - all in all a far better solution.
If you want to be really clever you can have the main program check for
newer versions of the launcher and replace that if needed.
Regards
Dave O.
<Jams060606@xxxxxxxxx> wrote in message
news:8bed7517-d51f-4110-9518-d27c8eae31e1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi
Please direct me to the right group, if I posted this in the wrong
one.
I developed an application using VB6, placed the exe in a shared
folder on our server and created a shortcut to the exe on client
machines.
The problem is whenever I have to update the exe, I have to call each
one and ask them to close the application, so that I can overwrite the
exe. Is there a way of tracking which computer/domain user is
accessing the exe?
I have used WhoHasIt for Novell Netware and found it very helpful. Is
there any substitute for WhoHasIt for Windows Clients?
Thanks in advance.
Leo
.
- Follow-Ups:
- Re: Who is using the EXE
- From: Rick Raisley
- Re: Who is using the EXE
- References:
- Who is using the EXE
- From: Jams060606
- Who is using the EXE
- Prev by Date: Class_Terminate not Invoked
- Next by Date: Re: Class_Terminate not Invoked
- Previous by thread: Who is using the EXE
- Next by thread: Re: Who is using the EXE
- Index(es):
Relevant Pages
|
Loading