NOW LIVE! Today's the day you meet your new best friend. You don’t have to leave Wolfy behind... In 'Pets & Sidekicks' your companions level up with you!

Reply to thread

Message: <blockquote data-quote="Davin" data-source="post: 322589" data-attributes="member: 1183">Well, I *found* the problem!  It's my fault!No, it's not the file name... but it *is* the set name!  Here's the deal...Your set was initially named FRGods.  Later, you renamed a different (bigger) set to FRGod and re-imported that set on top of your DB that still had FRGods in it.  This caused all the records therein to be reassigned to the new set, but ET Helper didn't recognize that the old set was now kaput and clean it out.Next, you download his file and import his set.  His set is also named FRGods.  But DBSets doesn't care 'cause it uses the GUID to tell things apart.  So his stuff imports just fine and everything is perfect.Well, almost perfect...  When DBSets goes to display that nice list of sets, it reads it in by set GUID (which are different) but lumps them together on the screen by set Code(!) instead of by GUID.  Since your old set name (which was still hanging around in the DB because I didn't know to clean it up) had the same code (FRGods) as his new set, it confused them on the screen and showed your set title beside his set definition!Therefore, while everything was correct under the covers and it was all being properly imported, exported, expanded, processed and everything else, the screen display of just that set name was showing the wrong name.  Therefore, you were extremely confused when you saw what looked like your data coming out of his file and got indignant (and rightly so, given the mis-information I was feeding you) at someone having stolen your effort.  The similarity of the content was surely due to the fact that you were both entering data from the same books.I'm VERY sorry!!!I'll find a way to fix that bug in my next version.</blockquote>

Verification