Chip,
from memory so...
One note:
- I believe existing (v15+) subtable support is one level deep only, I
do not know if this will/does affect you.
i.e [parent].substable_level1.subtable_level2... is not supported.
I'm not affected by this.
there is a special link betw
ehalf of 4D Tech Mailing List
<4d_tech@lists.4d.com>
Reply-To: 4D Tech Mailing List <4d_tech@lists.4d.com>
Date: Tuesday, 11 June 2019 at 14:17
To: 4D Tech Mailing List <4d_tech@lists.4d.com>
Cc: Garri Ogata
Subject: Re: Replacing Obsolete Subtable Commands in v15 to v17 Migration
from memory so...
One note:
- I believe existing (v15+) subtable support is one level deep only, I
do not know if this will/does affect you.
i.e [parent].substable_level1.subtable_level2... is not supported.
there is a special link between converted subtables and their parent.
this special lin
, 2019 11:34 AM
To: 4D iNug Technical
Cc: Olivier Deschanels
Subject: Re: Replacing Obsolete Subtable Commands in v15 to v17 Migration
Hello,
Another option is to think object. ie replace a sub table by an object field
... including a collection (that’s not the only design).
Regards
Olivier
E
Hello,
Another option is to think object. ie replace a sub table by an object field
... including a collection (that’s not the only design).
Regards
Olivier
Envoyé de mon iPhone
> Le 11 juin 2019 à 13:23, Narinder Chandi via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> Hi. So, after tac
Hi. So, after tackling the replacement of the majority of the obsoleted
commands in v15, the remaining ones are in the Subtable commands group
(ughhh!). The database I am upgrading has 11 Subtables. I have spent some time
perusing the archives prior to writing this - a lot of the posts are quite
6 matches
Mail list logo
