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 between converted subtables and their parent.
this special linage is NOT replaceable once broken.
The special linkage allows the subtable commands to continue to
function.
Yes, I am aware of that, thanks.
(speaking about 1 subtable)
I believe that if you remove the special link, and replace the subtable
commands that use it with record level commands you are good to go.
Yes, it seems so, although this requires using the " Get subrecord key "command
as illustrated in the example in the docs:
https://doc.4d.com/4Dv15/4D/15.6/Get-subrecord-key.301-3818017.en.html
There may be one major exception:
Reports using the subtable data. It has been along time since I played
in this area, but again, as I recall any reports using the subtable
commands will need extensive work. As subtable records load in a much
different fashion to related tables.
I don't think I have any reporting issues to be concerned about but I'll bear
that in mind, thanks.
Depending on the subtable structure definition(s) you may also
want/need to add a primary key for backup/journal purposes.
Yes, I mentioned that in my original post so I'm aware of that, thanks.
Regards,
Narinder Chandi,
ToolBox Systems Ltd.
--
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
