05-12-2016 08:23 AM
I have observed that, if a server connection crashes while Enterprise Guide has a project file opened (that is stored on the server), the project file may be damaged (empty, size zero).
But I never had problems with .sas files, as those are simple text.
I therefore recommend to store projects locally (while working on them) and make occasional copies to the server.
05-16-2016 04:33 AM
05-17-2016 02:19 AM
For shared codes, I strongly recommend to use a versioning control system instead of just editing the codes in place. Your problems might come from concurrent accesses to files.
05-17-2016 09:06 AM
There is a universe of VCS's out there: https://en.wikipedia.org/wiki/List_of_version_control_software
What suits your needs must be decided upon in your organisation.
I'm not one who runs the VCS, I just use it. And ours is mainframe-based at the moment.
05-17-2016 09:19 AM
SAS Enterprise Guide has integrated support for Git, including repositories like Github. See this blog post for some more details.
Aside from Git integration, you can use standard source control systems with file-system integration along side SAS and SAS Enterprise Guide. Here's another article about that.