We have several machine series we design here with over 5 decades of history so our numbering scheme is pretty chaotic. The problem we have run into is that when you create folders more then one level deep in the shared workspace and you check a file out, it creates anything beyond that one folder level locally (along with the OldVersions folder). Then when you check files in it strands this folder structure locally that has to be manually cleaned out.
Does *ANYONE* have any suggestions on how to manage a file structure so you don't end up with a massive local tree structure that has to be manually dealt with and also not ending up with a load of one-level deep file structures in the shared workspace as this would mean tons of folders at the base level of the shared space?
Any suggestions would be GREATLY appreciated :O)
~ Phlyx ~
Does *ANYONE* have any suggestions on how to manage a file structure so you don't end up with a massive local tree structure that has to be manually dealt with and also not ending up with a load of one-level deep file structures in the shared workspace as this would mean tons of folders at the base level of the shared space?
Any suggestions would be GREATLY appreciated :O)
