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
assuming that in v15, the fields are correctly defined as PKs.
in converting from v12 to v13 (in v13) I had to do this for each table:
where $Field-> is a pointer to my PK field (UUIDs)
For ($ii;1;Records in table($table->))
$Field->:=Generate UUID
SAVE RECORD($table->)
NEXT RECORD($Table->)
> Le 20 mai 2017 à 01:24, Douglas von Roeder via 4D_Tech <4d_tech@lists.4d.com>
> a écrit :
>
> Ronald:
>
> Distinct values is a good suggestion - it will be interesting to see what's
> in some of the fields but not the others.
From the doc, DISTINCT VALUES uses the index when it exists. Delet
Ronald:
Distinct values is a good suggestion - it will be interesting to see what's
in some of the fields but not the others.
Thanks.
--
Douglas von Roeder
949-336-2902
On Fri, May 19, 2017 at 3:46 PM, Ronald Rosell via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> I ran into this on a conversion
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 differe
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 i
6 matches
Mail list logo
