[Spiffy]

I have to respect that a company has EVERY right to lay someone off, and then be a bit circumspect in discussing the reasons for that afterwords.

But that's hardly the same thing as pretending a firing is a retirement.

Jenifer... my advice is just come clean about him being let go, and that the reasons for it aren't for public disclosure. I thought Robert came off as a nice guy, but its not like he's someone I know personally--and I don't know much about his work other than the face he presents here on this board. If he was let go, I'd feel for him, but give the company the benefit of the doubt. Because you guys know stuff about his employment I can't even PRETEND to know.

Trust in people to have some common sense. We know when a story smells, but I'd like to think we're also all reasonable enough to understand the details are none of our business--and that our loyalty to the company should be more about the products than one man.

On a side note NOT related to Robert... the guy who's the primary support tech needs a LOT of prodding, Jenifer. I think virtually every person here who's had a cause to email the support email address has run into similar problems--days of silence before even an initial answer. At the very least, one thing we all know Robert did well was be that prod, since I think a good number of us wound up having to use him as a go-between to get a formal support response going.