Freed Files using Local Copy?

Scott,

 If "leave local copy on free" is disabled, then when a document is freed, the local copy of the file in the working directory should be deleted.  Next time the user opens that file, it should be downloaded from the server. 

 Our typical recommendation is to leave this disabled.

 John

We had a complaint from an office about a ProjectWise workflow.

A user checks out a file, modifies the file but then frees the file on exit to discard the changes.  The next time they go to ProjectWise and check out the file they see the unwanted changes.  The first thing I said was that this couldn't be happening, that ProjectWise always considers the server copy to be the master file.  We happen to have Bentley's Kevin Jackson in the area and we both watched as the user showed us that it worked as he described.

Kevin suggested that we turn off  "Use up to date local copy on check out" from the Settings > Document properties.  That fixed the issue but I still feel that something's not right here.  This goes against what I always felt was the basis of the ProjectWise workflow.

The only thing I can figure is that the term "up to date local copy" means that if ProjectWise sees a local file with a newer date then the server copy, it considers it the "master" file and uses it.

One of our offices was setup by a consultant with the "Leave local copy on free" disabled.  Maybe this is why.