Citect 7.2 Server Behaviour

After 2 days of stressful playing with a citect application (V7.1) trying to find out why events where not firing, cicode executing when commented out I found out why....

Been a server application all the clients had to be shut down. The clients cicode was executing even thought i removed it from server and causing problems.

Does this mean every change I make to the server application I have to shut every client in the plant down?

Every small change I make to a graphic I must compile the application and restart? Surely this cannot be the case?

I am running v7.30 SP1 and remembered that Citect made some changes around v7.20 that helped me a lot with not needing to restart clients after a new server compile. For some things (adding tags for example) the client still needs to be restarted (shut down Citect and restart the app, not reboot machine). ....
I think graphics changes in 7.20 simply require a compile, and then refresh the page on the client machine.
To remotely restart Citect on a workstation, see Q6089 "Using Shutdown() cicode function to shut down the remote SCADA machine"
That might help if you have a bunch of spread out workstations, you could remotely shut down Citect on them (from a central workstation) and if you have auto-login and Citect in the Startup list, it should come back to Citect runtime application.
I know this really doesn't help you now at version 7.10, but 7.20 did make my job easier...