Originally Posted by
nelson
We are using a simple XCOPY to sync the drives, but the problem is that the PC stores the location of the DFS somewhere internally in the *.apc or *.xml and then the new location files are 'out of date' and are not visible until the PC is refreshed using the new location. I don't know where that change is being held because I don't see it in the files. That's what I'm hoping you all can help me figure out. From what I can see the only one is the *.htm file pulling the URL for the catalog location.
If you're storing the PC on the network, then that means (at minimum) you've copied the PC installed OOTB:
Code:
C:\ProgramData\Autodesk\C3D 20##\enu\Pipes Catalog
... To a network location, and subsequently used _AeccSetNetworkCatalog to specify the new location on the network. Did you have any problems with the resultant PC? Using XCOPY, provided the permissions are the same at the destination location, should not in any way change this functionality as I understand it.
I must be overlooking something; if the source and destination directory structures (drive letter, etc.) are the same, there shouldn't be any issues, given that the files uses relative paths AFAIK.
For example, from "US Imperial Pipes.htm" :
Code:
// ********************** BEGIN CATALOG CONFIG **************************************************************
// To configure your catalog, edit the following 2 vars
//
var strCatalog = "US Imperial Pipes.apc"
var strCatalogDomain = "Pipe_Domain"
//
// *********************** END CATALOG CONFIG ***************************************************************
Perhaps this thread will help to clarify, since you specifically mention DFS:
http://forums.autodesk.com/t5/AutoCA...1/td-p/3458248
Originally Posted by
nelson
Sounds like you are going way past just keeping the files in sync, I'm not devoting that much of my time to correct the mistakes by Autodesk. Chances are they'll change it in the next two release cycles anyways.
I'm trying to, yes; success of my effort is yet to be seen however. LoL
This is not an internal effort, I actually started working with Autodesk Feedback following the 'Jaws' Beta. Following a long conference call with their development, and project management team, this concept was passed up the chain. They seemed interested in the idea; enough that, at Autodesk's request, we may be hosting a small Autodesk team at my office shortly as a result.
Originally Posted by
nelson
I DO NOT allow users to go into the PC to make the edits. If they insist on making the changes themselves, I will officially make them the new holder of the catalog. I know no one would want to hold that title.
I'm the only one modifying the PC that resides on the network, but I tend to encourage customization more than some others.
Often times, I find others' ideas to be enlightening, and ultimately this encouragement leads to a better, more cohesive team, than those which do not. I find that users are more likely to adhere to a standard that they feel some level of ownership for, rather than something forced upon them. Just my limited experience.