Hi Narinder, Did you run the MSC verify *before* enabling dot notation to check for issues? https://blog.4d.com/get-ready-for-object-notation/
-Tim -----Original Message----- From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Narinder Chandi via 4D_Tech Sent: Thursday, June 20, 2019 10:06 AM To: 4D Tech Mailing List <4d_tech@lists.4d.com> Cc: Narinder Chandi <4dtechmailingl...@toolbox.uk.com> Subject: Dot Notation in Legacy 4D Code Soooo, I suspected this would be the case but just seeking confirmation... I am working with a 4D database that has made extensive use of dot in table, variable and project names (not of my doing btw!), e.g. [my.table.name] my.process.variable my.project.method Converting the database to v17 and enabling the compatibility option "Use object notation to access object properties" the database still passes compilation. However, numerous interpreter errors occur when using any database functionality. I thinks it's clear that all prior dot usage will have to be totally eliminated?? Urghhhh... 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:4d_tech-unsubscr...@lists.4d.com ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
