Document.SaveAs Mystery

[scotth]

We're running XMAX 6 and I've noticed some strange behavior on one particular user's computer. The xsi:noNamespaceSchemaLocation attribute on the root element of the document is simply the name of the schema before calling document.SaveAs (I'm checking the document object's XML in memory right before the call). However, after calling document.SaveAs, the physical disk on file is showing the path to the xsi:noNamespaceSchemaLocation as “../../../../../../myuser/AppData/Local/Temp/myschema.xsd”. Is there something going on behind the scenes with the SaveAs command that would cause this or perhaps a setting on the computer in question that could influence this?

Reply

[Author]

Posts