The calls are made directly to the dll you provide, there are no other files involved. So either there is a problem with the dll that makes the call fail altogether, or there could maybe be a second instance of Mercury running on the computer.

/Rolf 

Hi,

I am currently writing a daemon to run within Mercury. However the problem I have is when I make changes to the source code, compile and build the .dll and copy it into the Mercury directory over writing the old version the Daemons behaviour does not seem to be changing at all. I should add that I do close down Mercury everytime and re-open it so any changes have the opportunity to take affect.

 Does anybody know what might be causing this? Does Mercury make any other files automatically when the Daemon is run that need to be deleted so that its new functionality could take affect?

 Many thanks,

Alastair