checkout worksets at risk change in wup1 really risky

[D_Driver]

I am having some grave concerns about WU1
20080602_1900.

is the following just my imagination?
with the shipping build I could; based on a central file with a wall and 2 doors all on "workset1":

user 1 could take a local file home , check out workset 1 at risk, move or modify both doors.
user 2 working late could borrow door 1, modify door 1 save, relinquish everything and leave.

in the morning, user 1 could come in, plug in and save to central. Door 2 would update. door 1 would be updated to match the configuration left on the central file.

with the current build, user 1 is out of luck, "elements in the central file have been modified, make a new local file and copy and paste your changes into the new local file"
hmmm...
has anyone else noticed this change between builds?

[Scott D Davis]

user 1 could take a local file home , check out workset 1 at risk, move or modify both doors.

I added emphasis, but you already knew this. Anytime you check out a workset and use it somewhere (like at home) where it cannot communicate with the central file, you could have problems.

[D_Driver]

Yes indeedy, just wondering if there was a change in behavior between release build and latest WU1 (if I remember correctly even the dialog box prompts are slightly different).

[Steve_Stafford]

They might have changed wording but the essence of the issue is the same, you'll be warned you are editing at risk. Translated this means you'd better be a bloody expert and know what you are doing or you should "just walk away"... :smile:

[D_Driver]

Yep, but at issue are several tests I did before upgrading were I successfully went through the motions described in the original post.


with the shipping build I could; based on a central file with a wall and 2 doors all on "workset1":

user 1 could take a local file home , check out workset 1 at risk, move or modify both doors.
user 2 working late could borrow door 1, modify door 1 save, relinquish everything and leave.

in the morning, user 1 could come in, plug in and save to central. Door 2 would update. door 1 would be updated to match the configuration left on the central file.


Items saved to central prior to the <edit at risk> work being saved took presidence and did not completely sever the connection of the <at risk> file when reconnected to the central. Currently any single object edited by both someone connected to the central file as well as someone on the at risk workset completely destroy the ability to link the at risk local back to the central file.

[D_Driver]

Never mind, this was just a bad dream