Peter, Yes, for legacy structures that are converted to v17 you have to explicitly enable Unicode support and also enable the "Use object notation..." setting under Compatibility. This is assuming that your structure has a clean bill of health in the MSC in regards to not using the period ( . ) or square bracket ( [ ] ) characters in any 4D variables, tables names, etc.
Regards, Narinder Chandi, ToolBox Systems Ltd. I am available for new consulting opportunities… http://4d.1045681.n5.nabble.com/ANN-4D-Developer-Available-td5765443.html -- -----Original Message----- From: 4D_Tech <[email protected]> on behalf of 4D Tech Mailing List <[email protected]> Reply-To: 4D Tech Mailing List <[email protected]> Date: Sunday, 15 September 2019 at 11:46 To: 4D Tech Mailing List <[email protected]> Cc: Peter Jakobsson <[email protected]> Subject: Re: Object property inheritance - why does this this not work ? Hi Narinder So it does. I created a brand new structure and it now works. I did that example in a legacy upgraded structure so maybe there’s some compatibility setting that I needed to change to fully support the new object syntax. Many thanks for taking the time to check it and respond ! Peter > On 15 Sep 2019, at 12:41, Narinder Chandi via 4D_Tech <[email protected]> wrote: > > I just tested your code exactly as-is and all the variables have the expected values. I used 17.2 on Mac ********************************************************************** 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] ********************************************************************** ********************************************************************** 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] **********************************************************************
