Get latest is not recursive

davecourt · Post by **davecourt** » Wed Sep 15, 2004 6:00 am

Hi

I am trying to 'Get the latest' of a folder which has no files until you get 2 folders into it.

When I try and 'Get latest', it doesn't seem to pull anything out even though I have ticked the recursive box? Does anyone know why this should happen?

Thanks

Dave

dan · Post by **dan** » Wed Sep 15, 2004 7:24 am

Are any of the files Unknown or modified, and the Modified Local File option set to ""Do not overwrite"?

Also, does it make a difference where you invoke the Get (e.g., two levels up vs. on the folder containing the files)?

davecourt · Post by **davecourt** » Wed Sep 15, 2004 7:34 am

Thanks for getting back to me so quickly.

The files are just 'missing' according to the description and yes it does make a difference if I get latest directly from the folder that the file belongs to.

Hopefully that might suggest some possibilities?

Thanks again

dan · Post by **dan** » Wed Sep 15, 2004 8:34 am

Something's not right. Does the messages pane indicate any sort of problem with the Get?

You may want to email me off-line as I might want to see an image of you repository structure and perhaps a history print out for the folder you are getting from.

Also, does anyone else have the same problem (e.g., does it appear to be a client or server issue)?

davecourt · Post by **davecourt** » Wed Sep 15, 2004 9:01 am

Hi Dan

Thanks for your help. I have continued investigating it and it seems to be an issue with the working directory. I unset the working directory and it worked fine but then seemed to set itself again?

I have rebooted my machine and it seems to have settled down now?

I will keep you posted if I have any further strange going ons.

Thanks again for your help!

dan · Post by **dan** » Wed Sep 15, 2004 9:07 am

Perhaps you had a working folder set lower in the tree to someplace else, and it was getting the file to a place you didn't expect?

Or, perhaps there was something funky about which working folder it was choosing, but the reboot addressed it...

In any case, I'm glad this works for you again.