the _o_ prefix is primarily telling you to stop using it in new code. (you will no longer find it in type-ahead, for example)
it also allows you to find and remove them in existing code, but the level of urgency varies; some are not 64-bit ready, some have a superior (preemptive, object based, simple...) successor, some are just old-fashioned (require process or inter-process variables, pointers, etc.) and "not cool". so you can't generalise all _o_ commands as if they were a liability. --- as for sub-tables, ORDA completely changes how you look at related records. they belong to a different table, or a data class, like in SQL, but in code there are accessible as entities of the master table, as if they were sub-fields or sub-sub-fields. 2018/11/04 6:29、Robert ListMail via 4D_Tech <[email protected]<mailto:[email protected]>>のメール: Are you suggesting that I leave the old “_o_” commands in place on a converted V17 database? ********************************************************************** 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] **********************************************************************
