I wanted to also point out the differences to anyone who is unaware of the difference between code and modules.

In, say, a thousand lines of code a couple of lines may refer to a module.

That module is another piece of code that is included when programming the controller.

A new programmer that has access to the code can readily and simply make changes to a lighting scene or other simple function. It would take essentially the same amount of time to do so as it would the original programmer.

If the client changes out a piece of equipment that is controlled by a module then the act of reprogramming is a simple as changing few lines of code that referred to that module and adding in a new module. If it is a commonly controlled piece then any programmer worth his salt will have such a module or it will be available from AMX/Crestron's website already.

Whether the original programmer or a new one makes the change it once again would take roughly the same amount of time.

Julie, you agreed with Spyeguy's "words of wisdom" that people that keep modules should get off their high horse. I say you clearly don't understand how a module works and that Spyeguy either doesn't use highly customised modules or doesn't understand them either.

For the record our company provides all code, touchpanels, as-builts and disks to our clients with the exception of custom modules that can be easily replaced by any competent programmer.