Teamwork and Lost Data

[Anonymous]

We have a team using Teamwork to work on a model. One of them crashed in ArchiCAD and now he can't get the changes he made back to the master file. How do we recover from this problem? We've had this situation before and we wound up redoing the changes. He was working on a copy he had saved to his desktop.

[Anonymous]

Of course, the sooner you discover the problem the better. The solution isn't elegant by any means, but here goes...

1. Make sure that the other user(s) send & receive changes (and sign out if desired).
2. Let the user who lost the data sign in with exclusive access (not required, but useful).
3. Copy & paste the missing data from the draft file into the teamwork file.
4. Send & receive changes and everyone continues working.

[__archiben]

Jay wrote:
. . . and now he can't get the changes he made back to the master file. How do we recover from this problem?.

jay

have you tried sending and receiving? i know that it sounds a little silly, but this has happened to us a couple of times - depending on the point at which your user crashed, the draft number may have clocked up in the teamwork admin file, but not written back to the local draft file.

if you try to send and recieve, archiCAD may tell you something along the lines of: 'you are working on an earlier draft and sending changes will result in you losing the work sent on the later one'.

in this case it doesn't matter as the work on the earlier one had not been sent, and the later one doesn't exist as the the new draft number hadn't been sent back to the local draft file . . .

hope this doesn't sound too confusing.
good luck . . .

~/archiben

[Anonymous]

~/archiben wrote:
have you tried sending and receiving?

Does this mean that send/receive uses the saved copy of the plan on the hard drive (as opposed to what's currently in RAM)? It sounds like you sign-in and get everybody else's changes, then when you send & receive it writes the changes from your hard drive's file. If that's correct, then it's absolutely necessary to save before send/receive.

Or am I misunderstanding the sequence?

[__archiben]

david

the send and receive uses the most current version of the file that you've been working on (what you call 'saved in the RAM', but probably is one of the many .SCRATCH files that archiCAD litters around).

what happens is that after you have sent and received your changes, archiCAD assigns a new number to your draft file (it starts at 1 and just clocks up until you sign-out - try looking at the 'teamwork notes' under the teamwork menu and you will see what's happening).

this makes it absolutely essential to save after a send and receive, (however since version 8.0.x and it's instability i have got into the habit of saving prior to sending and receiving too).

what i was referring to in my previous post was something that has happened once or twice here. . .

if archiCAD crashes when sending and receiving changes after it has assigned you a new draft number in the admin file (usually kept on the server) but before that new draft number gets written to your local copy, your draft becomes out of synch.

if you try and send changes from this draft, archiCAD will warn you that it is out of date. this is a safeguard should somebody try with a genuinely out-of-date draft, however: in this case you know that the draft is not out of date because a crash caused it. so you can happily ignore archiCAD's warning and send those changes in anyway.

this may or may not be the case for you - as i said earlier, it depends upon when the crash happened, but it may be still worth a try to recover your data before trying 'major surgery'!

HTH
~/archiben