Re: already running
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Fri, 29 Jun 2007 08:12:00 -0500
"Dave O." <nobody@xxxxxxxxxxx> wrote in message
news:%23%23hDKniuHHA.5072@xxxxxxxxxxxxxxxxxxxxxxx
It depends how critical it is to have a single instance and how deviousyour
users are.
App.PrevInstance can be fooled by making a copy of the executable and
renaming it.
If you need to avoid that possibility research on MUTEX, however if it is
not a potential problem then App.PrevInstance will be adequate.
Regards
Dave O.
To add another petty distinction. App.PrevInstance also depends on an app
being fully initialized. So if you have an App that takes a bit of time on
start-up it is possible for a user with rapid clicks to launch several
instances.
IHMO, adding Mutex functionality is simple and avoids all short falls, so
why not use it? Set it and forget it. <g>
Here is one way...
http://www.vbaccelerator.com/home/VB/Code/Libraries/Shell_Projects/Registering_File_Associations/article.asp
Here is another...
http://vbusers.com/code/codeget.asp?ThreadID=275&PostID=1&NumReplies=0
-ralph
.
- References:
- Re: already running
- From: Dave O.
- Re: already running
- Prev by Date: newbie: How to deploy vb5 exe on 2000, XP
- Next by Date: Re: newbie: How to deploy vb5 exe on 2000, XP
- Previous by thread: Re: already running
- Next by thread: Renaming files & importing them
- Index(es):
Relevant Pages
|