MadCap Software Forums

Hi there,
we are frequently angered by the following fact:
If one user deletes files, other users find them in their list with the status "pending add" - and that a lot more often than with the status "deleted" which is the correct status. That occurs with Flare 3.1, 4 and 4.1 ...

Is that a fault of Flare or MS VSS 2005?

Thanks in advance.

Inge

Where is the user deleting the file? Locally or in VSS 2k5?

locally.

So if the file is supposed to be removed from the project you need to make sure that it really is deleted in the project in VSS. Ideally, Flare should take care of that assuming that you hooked into VSS through Flare, but if the file isn't gone in VSS it will come back the next time around.

isn't the checkbox Remove From Source Control supposed to do the job?

Yes, "supposed", but I'd check if it really truly surely does that.

honestly, if I'd have to check each time I could do it in VSS immediately ...
And it is a "sometimes-I-do-the-job-function" of VSS or of Flare? Is it worth a bug report or do we have to live with it until at least the next version of VSS is installed?

I don't know, it may be something that gets lost in translation. My gut feeling makes me blame VSS, given that VSS 6.0 was plain disastrous and that VSS 2005 is a Microsoft product as well, but it may be none of the application and just some flaky behaviour in the API. Assuming that VSS keeps some logs, do the logs claim that the file was deleted? It may also very well be that the deletion in VSS and locally on one client worked fine, but since the file is still stored locally on other clients it may appear to Flare as that the file in question is new. But then again, since it is not consistent it can be anything. Luckily deleting files isn't the most common task, yet it should still work.
I'd file a bug report and give as much detail about the observations as possible. I think the MadCappers are in a way better position to figure out what is going on or not.

in the VSS database I can't see those topics anymore ... in the logs - no idea ... that takes time, right?
...
I'll post a bug report.

Logs, if there are any, are written immediately after the action succeeded or failed. But it can well be that VSS either has no log files or logging is not enabled.