working away from server

[andrew.tulp]

Our office is moving, and our server is down for the today (friday) and the weekend.  I'm out of the office working from a coffer shop for the moment. Of course, I need to work on a project.  The project I'm working on has been workshared, with the central model on our server, and I have a local copy on my laptop.  I forgot to change the worksets to editable when I still had access to our server (assuming I should have done that).  So when I attempted to get into the model and make changes today of course I had some popups etc.   Not sure what it would do, or if I needed to do this, I changed the default worksets to editable and saved my local copy.  Then I thought, as I'm really the only person working on this project for the time being, it doesn't really need to be workshared,  I re-opened my local copy, with "detach from central" selected, and I selected preserve worksets.  I then saved that model with a new filename, and just to be sure that worked re-opened it.   When I go to open that model, Create New Local is grayed out, and Detach from Central is unchecked.   When I'm in the model, the sync button is still there, and when I close the model, it still warns that I haven't synced.   

What did I do wrong, and what is the 'proper procedure, to, in effect, "unworkshare" this thing for the next few days?

[Matt__W]

What I would've done is open the central model on the network using the "detach from central" option then save it as a new central on your laptop. Close the model. Reopen the laptop central and create a new local model. Work as you normally would, syncing to central (on the laptop). Then when you're back in the office on Monday you would repeat the process of opening detached from central and save it as a new central back to the network, overwriting the existing model. The problem you might run into is if others need to work on the model and do the same thing as you. Their changes will only be reflected in the models they have on their laptops and whoever overwrites the central model on the network Monday morning LAST, is "the winner". Make sense??

[andrew.tulp]

Matt - this is great!  I really like that method.   Looks like I can take your method, even without access to my original central model.  As such, I'm now working from a new local, derived from a new central, both on my laptop.  (This works fine, as I'm the only one working on this project right now.)

What I had expected was that 'detaching', in essence eliminated the central/local structure, and left me with only one model (not workshared).  But it seems to me now that once worksharing is enabled, that structure is always in place.  As such, detaching from central and saving creates a new Central model of sorts.  Do I understand that correctly?   

Is there a way to eliminate the worksharing  (central/local) structure, once a model has that structure?  

[Matt__W · Accepted solution]

If you open the model using Detach and then DISCARD the worksets, it removes the ability for you to collaborate with any other users. Also, if you're using worksets to control visibility of objects, that's completely undone and you may end up with things showing in views you don't want them to. But if you're not, then it begs the question.... why are you using worksharing to begin with?