Thanks for the input NorCal. I didn't realize that Systembuilder was a stepchild when I was researching my decision to take the class. I have 0 years experience with Systembuilder, or with Crestron for that matter, though I hope that is changing. So when I took the class it was easy to see that Composer would go by the wayside fairly quickly, but Systembuilder looked like programs I'd used before, just more powerful. I know there is a lot to get used to. Stamps point would be that since I am starting fresh, don't go down the Systembuilder road, but I kinda have to since I am small and if I want to do Crestron it is going to have to be Prodigy.

All but one guy in my class of 7 or 8 were doing or had done full Crestron. I assume that they were there because it is an entry level product for their markets. Even you say that you have done Systembuilder for several years and that your programming headaches have been "reduced". From what to what? 3 posts back Gerry talks about things being "broken" or losing connection. I 'm sure that I can learn Systembuilder, but "trial and error", things being broken after fixing other things, staying up all night troubleshooting, as a one man band that worries me because my time is precious. Are these things a normal part of programming in Systembuilder or as Gerry said is it because "we pushed too far"?  And what does "pushed too far" mean? What is everyone trying to make this program do?

Again, I really appreciate that people that have some experience with Prodigy have been willing to share. I put my PO in with my application etc but haven't received my demo equipment yet. When I do, I will set it up and play before I put it in anyones house. I want to know that I can make it work reliably.

So here is how I see Prodigy working for me. "Hi Mr and Mrs Customer. So you would like to upgrade your system (or install new). Check this out. You can control your whole system from this very sharp looking colorscreen remote. You can also see your Ipod on this remote and control it. When you sit down to watch TV you can lower the temp of the house from this remote, and dim the lights for that movie theater feel, and you don't need all those other remotes. And this system can grow with you, add more lights, add music in other parts of the house and control it from this remote, a keypad, or one of these color touchscreens."  Or they have a dedicated theater. I'm simplifying. But that is the gist of it. And since Crestron makes all the parts, I only have to talk to one tech support if there is a problem. Is my logic horribly flawed here?

What would I be doing that would make things "break" in this senario? Why would Simpl be better for this senario?

And I'm guessing that some full line guy just read this and spit his drink all over the table "OMG, this guy is bastardizing Crestron". Don't flame me guys, I really am looking for answers and solutions. Prodigy seems to be a good one. And I'm guessing that this is what it was designed and built for. As a one man shop, it looks like a great solution, especially for retro-fits.

So since I am growing INTO Systembuilder and not dumbing DOWN to it from Simpl, am I going to run into the same problems? I think I'm less likely to try to make Systembuilder do something it isn't made for than someone who is familiar with all the power of full Crestron.

Again, I appreciate the input. TIA!
G