How about having each user create his own mxd using their own version of the layer you want to use Editor Tracking on? This should at least solve the problem of only joe being tracked. Make sure that the layer with joe's version is not copied into any of these new mxds because it would be carrying his credentials along.
Yeah, I've actually already fixed the problem.
I just gave everyone the original MXD from the client and then they resourced it themselves.
I guess I just wasn't aware that the MXD stored the actual connection file credentials inside. Good to know.
-------------
The only reason we are using the clients MXD is for symbology purposes. Even when I grouped all the layers and created a layer file, it still saved the connection credentials inside the layer file when I added it to a blank ArcMap.
The behavior that you were observing is actually correct!!
When Joe resourced the MXD, he must have used his connection (connected as user 'Joe')....the MXD stores this user information along with other connection parameters...
The correct way would be for each user to create their own connections with their username/password and then resource their individual MXDs to point to these new connections (which I guess you already figured out).
The behavior that you were observing is actually correct!!
When Joe resourced the MXD, he must have used his connection (connected as user 'Joe')....the MXD stores this user information along with other connection parameters...
The correct way would be for each user to create their own connections with their username/password and then resource their individual MXDs to point to these new connections (which I guess you already figured out).
Regards,
Yeah, it all makes sense now that I know the MXD stores the connection credentials. I wasn't aware of that. I always thought ArcMap just used whatever connection properties were set in ArcCatalog on that local computer.
