That is pretty funny. I do not use single click and I am not at a user level. I know what that is, and as I stated before, there is not an attempt to execute the .exe twice, this is just how it shows up in the monitor on the server. That is not the problem.

It does not show the .dll or tables opened twice, just the .exe. Under further looking, I found that something is locking the tables. It seems to be a locking problem that is preventing the .exe from running. When I see the locks on the only one connection trying to go in, the monitor on the server does not show any tables being opened yet or locked, and being as I am the only one connection trying to run my .exe on the server, I am not sure what else would be locking the tables.