Who is using the EXE

Jams060606 · Joined: 21 Feb 2008 Posts: 2

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

Archived from group: microsoft>public>vb>general>discussion

Dave O. · Joined: 04 Oct 2007 Posts: 580

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.

wrote in message @p73g2000hsd.googlegroups.com...
> 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

Larry Serflaten · Joined: 04 Oct 2007 Posts: 2644

wrote

> 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

I agree with Dave. Having a 'launcher' app on each client fills the need
nicely. I've been at one place where that 'launcher' app actually pulls
down a list of commonly used (shared) applications and prompts the
user to select one from the list.

After adding or altering program files, a small update to that list gets
everyone on the same footing. The only downside is that users continue
to run the version they have until they close down the application and
try to launch it again (via the launcher app).

LFS

Rick Raisley · Joined: 04 Oct 2007 Posts: 159

I do something similar, except I do locate the launcher program on the
server (along with the latest actual program EXE, less its EXE extension).
All the user has locally is the shortcut to the launcher program on the
server. So, the shortcut runs the launcher program, which checks to see if
the main program EXE on the server is later than the local copy on their
machine, and if it is, it copies it over their local copy. Then it launches
the local EXE and ends. This allows me to change the launcher (as it's in
use for only a fraction of a second) if needed, and of course, change the
main EXE at my leisure.

--
Regards,

Rick Raisley

"Dave O." wrote in message@TK2MSFTNGP04.phx.gbl...
> 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.
>
> wrote in message
> @p73g2000hsd.googlegroups.com...
> > 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
>
>

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Larry Serflaten wrote:
> The only downside is that users continue
> to run the version they have until they close down the application and
> try to launch it again (via the launcher app).

I suppose, if that were found to be the case, the main app could be written to check
for a semaphore that indicated a new version was available and prompt the user to
bail?
--
..NET: It's About Trust!
http://vfred.mvps.org

Dave O. · Joined: 04 Oct 2007 Posts: 580

Interesting thought, I avoid running apps over the network but as you say it
would only be momentary so not a serious issue - thanks.
Dave O.

"Rick Raisley" wrote in message @TK2MSFTNGP03.phx.gbl...
>I do something similar, except I do locate the launcher program on the
> server (along with the latest actual program EXE, less its EXE extension).
> All the user has locally is the shortcut to the launcher program on the
> server. So, the shortcut runs the launcher program, which checks to see if
> the main program EXE on the server is later than the local copy on their
> machine, and if it is, it copies it over their local copy. Then it
> launches
> the local EXE and ends. This allows me to change the launcher (as it's in
> use for only a fraction of a second) if needed, and of course, change the
> main EXE at my leisure.
>
> --
> Regards,
>
> Rick Raisley

Jams060606 · Joined: 21 Feb 2008 Posts: 2

Thanks a lot guys...

I think the launcher app makes sense...

Do you have an example of the code of a launcher application?
Appreciate the help.

Regards

Jams

Dave O. · Joined: 04 Oct 2007 Posts: 580

It's really quite straight forward, you need to break it down to a few
steps.
1) The launcher reads the version number (or creation date) of the local
copy.
2) It then reads the same data for the copy on the server.
3) Next compares the two, if they are the same goto step 5.
4) The remote one is newer than the old one so overwrite the local one
with the one on the server.
5) Shell out to the local copy.
6) Close the launcher.

I'm not going to do all your work for you, so sort out what you do know how
to do then come back with any gaps and we'll point you in the right
direction.

If your program has a help file (or indeed any ancillary files) you should
also check that so you can update the help file along with any changes to
your executable.

Best wishes
Dave O.

wrote in message @s37g2000prg.googlegroups.com...
> Thanks a lot guys...
>
> I think the launcher app makes sense...
>
> Do you have an example of the code of a launcher application?
> Appreciate the help.
>
> Regards
>
> Jams