TeamSite checking for previously existing file?

tobias

Hi everyone,
this is with TS 6.7.2 on Solaris 10.

I deleted a file and submitted the deletion (so it gets deleted in STAGING too) and then re-created a file with the same file name.
Now, when I try to edit this re-created file, the following message is displayed:

The file [filename] has been deleted in STAGING but still exists in your workarea. Do you wish to continue editing the copy in your workarea?

Is this default TS behaviour? Does it depend on the submit/lock model of the current workarea/branch? Is there a way to prevent this check from being performed?

We are having one workarea per branch only, as a rule, so there is no chance of someone else working on the same file in another workarea.

Any ideas and hints are greatly appreciated.

Migrateduser

This is default behavior. If a file has a version in staging that is different than the version in the workarea, you will get this warning on the file when you try to edit it. It does not depend on the lock model, it is standard across all the locking models. As to bypassing this check, I don't believe you can. However, you might try making a local copy of the file, perform a get latest on the file (which will delete it from the workarea) and then import your local copy back in to the workarea. This should resync the version of the file with the one in STAGING. If this doesn't work, submit an empty file to staging and then modify the empty file in your workarea to contain the new content.