On May 22, 2017, at 9:00 PM, Chip Scheide wrote: > it is also possible that your 2004 data file has issues
Chip is right. I ran into this in one database I was converting. Here is what I know. Say you had PKs assigned that were longints and you had the "unique" property set for the field and you were using 4D's sequence number system to assign the PKs. This should ensure you had no dup keys. But there was a time when 4D had a bug and it did not always enforce the unique property for the field so dups could creep in. Then they fixed the bug -- I don't remember what version number -- and you would get a runtime error if a dup key was found when you saved a record. But any existing dup keys were still there. Converting to v11 or later would uncover them. So if you have an old database from v2004 or prior you can have dup keys. Tim Sent from my iPad ********************************************************************** 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] **********************************************************************
