Reply to thread

Message

<blockquote data-quote="Davin" data-source="post: 322162" data-attributes="member: 1183">ET Helper is *supposed* to be forgetting set names once all their contents are deleted (but you can Access-view the [types Set] to make sure).&nbsp; However, if that is messed up somehow and not showing, and if his set GUID ended up with the exact same GUID as you (maybe he copied just the GUID in order to enter his stuff??), then it will look like it's loading his data into your set.Another thing you can do to check is to view his XML file in Notepad (or similar) and find the &lt;dbTable name=&quot;types Set&quot;&gt; section.&nbsp; Look to see what he's using for his set name &amp; GUID.&nbsp; Maybe he downloaded yours to look at it, then started entering his stuff (like feats) into the same set, then deleted your stuff, then re-entered everything and it all ended up getting attached to your name.Or maybe he entered all his stuff as &quot;User&quot;, downloaded your set to look at it, then deleted your stuff piecemeal while renaming his data into your existing set name.There are some weird combinations/sequences that can produce that kind of set name preservation, but I wouldn't expect any of them to happen very often.</blockquote>

[QUOTE="Davin, post: 322162, member: 1183"] ET Helper is *supposed* to be forgetting set names once all their contents are deleted (but you can Access-view the [types Set] to make sure). However, if that is messed up somehow and not showing, and if his set GUID ended up with the exact same GUID as you (maybe he copied just the GUID in order to enter his stuff??), then it will look like it's loading his data into your set. Another thing you can do to check is to view his XML file in Notepad (or similar) and find the <dbTable name="types Set"> section. Look to see what he's using for his set name & GUID. Maybe he downloaded yours to look at it, then started entering his stuff (like feats) into the same set, then deleted your stuff, then re-entered everything and it all ended up getting attached to your name. Or maybe he entered all his stuff as "User", downloaded your set to look at it, then deleted your stuff piecemeal while renaming his data into your existing set name. There are some weird combinations/sequences that can produce that kind of set name preservation, but I wouldn't expect any of them to happen very often. [/QUOTE]

Verification