Re: New error about primary keys

2017-11-21 Thread Kirk Brooks via 4D_Tech
Lee, I seem to recall something like this when I converted a datafile that had dupes in the PK field. But I don't recall the specific wording on the dlog. On Tue, Nov 21, 2017 at 4:19 PM, Lee Hinde via 4D_Tech <4d_tech@lists.4d.com > wrote: > I've seen the dialog that comes up with database with

Re: New error about primary keys

2017-11-21 Thread Lee Hinde via 4D_Tech
Thanks for responding. On Nov 21, 2017, at 4:34 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > the two dialogs are flagging the same problem, only the context is different. > >> I've seen the dialog that comes up with database with ambiguous primary >> keys - the one that star

Re: New error about primary keys

2017-11-21 Thread Keisuke Miyako via 4D_Tech
the two dialogs are flagging the same problem, only the context is different. > I've seen the dialog that comes up with database with ambiguous primary > keys - the one that starts with "This version of 4D provides a more robust > log file and you". this one pops up when you have access to d

New error about primary keys

2017-11-21 Thread Lee Hinde via 4D_Tech
I've seen the dialog that comes up with database with ambiguous primary keys - the one that starts with "This version of 4D provides a more robust log file and you". But I just converted a v13 database to v15 and got a different alert: "Potential issues with primary keys have been found. Ple