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] **********************************************************************
