I ran into this on a conversion once. Turned out, I was using a Sequence Number field as the PK field, and somewhere along the way some code had been introduced that led to duplicates. Usually this was because records were being created by multiple methods, and one of them was doing it differently from another (one might assign the sequence number, another might be sequence number + 100. Goofs like that.) Fortunately there were few records affected, but all it takes is one duplicate for the indexing to fail.
If you write a little utility method that collects a Distinct Values array for your intended PK in one of the affected tables, then searches all records looking for for more than one instance of each value in the Distinct Values array, you’ll likely find that you’ve got some duplicates in there. Ron Rosell [email protected] __ Ron Rosell President StreamLMS 301-3537 Oak Street Vancouver, BC V6H 2M1 Canada Direct phone (all numbers reach me) Vancouver: (+1) (604) 628-1933 | Seattle: (+1) (425) 956-3570 | Palm Beach: (+1) (561) 351-6210 email: [email protected] | fax: (+1) (815) 301-9058 | Skype: ronrosell > On May 19, 2017, at 1:54 PM, Douglas von Roeder via 4D_Tech > <[email protected]> wrote: > > I'm hitting the same issue that Gary ran into though I'm trying to convert > a 2004 data file to run agains the V15.4 structure file. > > I added PK's using the code from Bob Miller's Summit presentation (many > thanks for a superb presentation Bob!) so I'm comfortable that the PK's are > done right. > > The issue - when I convert the 2004 data file, 4D reports that 53 out of > 105 tables have duplicate PK values. What are my options for resolving this > issue? > > > -- > Douglas von Roeder > 949-336-2902 > > On Sat, Aug 29, 2015 at 3:09 AM, Ortwin Zillgen <[email protected]> wrote: > >> >>> Am 28.08.2015 um 19:37 schrieb Gary Boudreaux <[email protected]>: >>> >>> FYI, this issue has been resolved. When I put my "live" data file into >> the folder with the new structure, I didn't think to delete the old indx >> file. Once I deleted that file and restarted 4D, the problem went away when >> 4D rebuilt the index file. So the issue was actually duplicates in the >> _index_ file, not in the data itself. >> >> thx a lot. >> Did you tell 4D about that? Suppose, they want to know. >> >> >> Regards >> O r t w i n Z i l l g e n >> --------------------------------------------- >> <mailto:[email protected]> <http://dddd.mettre.de/wp/?4713> >> <feed://dddd.mettre.de/dddd.xml> <https://twitter.com/Ozett> >> member of developer-network <http://www.die4Dwerkstatt.de> >> >> ********************************************************************** >> See how easy it is to extend your 4D solutions to Web and mobile. New >> opportunities await you with 4D v14! >> >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: http://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:[email protected] >> ********************************************************************** >> > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
