David wrote:Understood. I will make sure to turn my shirt inside out and put my underwear on my head as well.
If you are going to the trouble of saving as a solo project then always save with a new name (this breaks the link with the old Prefs) In fact do this twice each time with a new name and then reshare with a new name. Saving twice as a solo really gets rid of any residual TeamWork stuff.
I'm told it also helps to stand on one leg and turn anti clockwise 3 times before resharing....
Steve, your technical skills obviously surpass mine... 
Steven wrote:Steven,
Also, maybe a related problem, quite frequently when I go to change my workspace, it comes up with the following during the process:
"Can't read teamwork project" then "Project (then the name of the file) not found or stored name does not match. Please find the project manually." I did not change the name at all, and it brings up a window to find the project. It's always right where it expects it to be, so I click on it and say OK. Then it says Can't read teamwork project" and "Cannot read teamwork admin data." I eventually have to quit and restart ArchiCAD.
Is this related? It happens to me only and not the other two users in my office.
HELP!
I have had the same problem that you are experiencing. The remedy that I stumbled upon, with the help of our IT staff, was that my teammate's computer would overwrite and own the teamwork file every time he signed in/out of the project. Therefore, causing the rest of us who were already in the file to be locked out of it while still in the file, thus causing numerous rewriting errors to pop up, just as you previously mentioned. So if your working on a network maybe you can have your IT person run a permissions fix to your project file and your computer.
This seemed to do the trick for us and the error has not come back.
Still looking?
