Narinder: That’s correct - it you’re using dotted notation, you’ll have to clean up the old code. The good news is features in newer versions make that much easier. The Find in design feature is much faster and far more flexible. Once you run a query and the results window opens, you can delete items from the list if you wish, you can drag and drop the content into a method window and then right click to open the methods (or Ctrl K), and you can “Replace in content” from the popup menu on the gears icon in the lower left.
-- Douglas von Roeder 949-336-2902 On Thu, Jun 20, 2019 at 10:06 AM Narinder Chandi via 4D_Tech < [email protected]> wrote: > 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:[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] **********************************************************************
