Allow only one instance of compiled script

[Mbrower]

Great product and a great forum. Normally I can find the answers by searching the forum but this time I have been unsuccessfull.

How can I prevent a user from accidently running a compiled macro multiple times by clicking on an exe more than once?

[Bob Hansen]

Here are two methods ......

1. First line of macro could rename itself.
Last line of macro could rename itself back to normal.

OR

2. First line checks for a temp file exists or for an INI value. Quit or Run based on results.
Second line creates a temp file or writes a value to an INI file.
Do Stuff
Last line deletes the temp file or changes the INI value.

[Marcus Tettmar]

I would use a registry key. Otherwise you need to know which path to store the INI file in and if there are multiple copies of the exe in different locations this could be an issue. But all copies could access same registry key:

Code: Select all

RegistryReadKey>HKEY_CURRENT_USER,Software\MyEXE,Running,isRunning
If>isRunning<>TRUE
  HKEY_CURRENT_USER,Software\MyEXE,Running,TRUE
  ..
  .. rest of your macro code here
  ..
  RegistryWriteKey>HKEY_CURRENT_USER,Software\MyEXE,Running,FALSE
Endif

Now only one copy of the exe can actually do anything at a time.

[Me_again]

Will it ever run? If the key doesn't exist I don't think RegistryReadKey> will return anything. So doesn't the If> need to be something like;

If>{(%isRunning%=FALSE) or (%isRunning%="")}

for it to run the first time and write the key?

[Marcus Tettmar]

I meant TRUE. Have edited accordingly.

[Mbrower]

Thank you all,

I was already writing to an ini file so I used that method. Tested and it is working fine.

Thanks again

[Rain]

Another solution would be to add IfWindowOpen>Compiled Macros Dialog name,exit at the beginning of the script. That will shut the 2nd instant down immediately.

[jpuziano]

There is a potential weakness of using a registry key for this:

• - user fires up macro
  - macro updates registry to store value to denote "macro is running"
  - power failure happens or user shuts off power to PC so there is no chance for the macro to change the registry value
  - later, PC is powered up, user runs macro, macro checks registry, value indicates "macro is running" (even though it isn't) and macro shuts down... user can no longer run the macro.

Rain's solution is the simplest and doesn't have the above weakness...

Another solution would be to add IfWindowOpen>Compiled Macros Dialog name,exit at the beginning of the script. That will shut the 2nd instant down immediately.

Thanks for posting that Rain and take care all...