whf
2007-08-15, 07:36 PM
So this is a problem that seems to exist on every system that I work on (I have a few different places of employment) and has cropped up a number of times in different settings. I have some surfaces that are defined by imported xml file(s). The office updated the network, adds some storage etc., and now my xml files have a different path. This is ok for the surfaces that don't need to change....but I have a surface that needs updated. I create a new xml file (from different drawing) with the same name. I go into the surface properties/definition and update the pathing of the imported xml file to the new location/file. It prompts me to rebuild, and I do. Next I rebuild the snapshot. Now the surface is empty...no data. I've tried every variation of the creating and repathing of the xml file, and same result. I can export another xml from this surface (just for test), and nothing, just a little 7meg xml file of nothing. There is nothing wrong with the xml. I can import it as a fresh surface, and it comes in fine. In fact, this is how I have had to handle the updated surfaces for a temporary work-around....I just import as a new surface, and then paste that into my empty (original xml based) surface, so that the zillion things that are referencing that surface are happy. While this works as a quick fix, it is not at all acceptable and negates the purpose of creating the xml files in the first place (and not doing so is not an option, as the drawing quickly gets too large). Any help is greatly appreciated....as this software (civil 3d) is about to drive me into early retirement (really).. Thanks for your help!!!!
Bill
Bill