Support Board

Speaking of that, only vendors should be allowed to remotely *shutdown* studies; I don't think free DLL's should qualify. If you're worried about users running your studies with out-of-date versions of SC, couldn't you insert a terminator code subroutine, calling out to an external web API to return a list of deprecated SC versions and give the user an on-screen message alerting to upgrade SC? Or if that's too hard, isn't it possible to ask people to *subscribe* to an SC-indicator-upgrade thread to get email alerts whenever you post an "upgrade now please" alert?

ad 2) Account name is the only way to protect the library from uncontrolled distribution everywhere. I will be happy if Sierra makes Accountname2 which will not serve as a login but will function as a unique ID as Account name1. Then this whole discussion of abuse your account would be pointless.

Suggest it to them. I'll vote immediately for this too.