Unconverted subtables continue to work with the old subtable commands. Once you break the subtable link they will not work, however, and you have to use the regular table commands. Did [Plant_IU] used to be a subtable, i.e., [Plant]IU ? If it’s been converted you can no longer use _o_FIRST SUBRECORD. If it hasn’t been converted then you must have changed that line of code because 4D would not change it by itself.
How there could there be thousands of syntax errors simply by converting from v11 to v15? ------------------------------------------------ Richard Wright DataDomain [email protected] ------------------------------------------------ > Date: Wed, 1 Feb 2017 22:54:01 -0600 > From: Robert ListMail <[email protected]> > > I’m working with a database that’s still being used in v11 and where the > current development version is in v15. There have been thousands of syntax > error fixes and now I’m dealing with the 7 existing subtables. Shouldn’t the > compatibility mode provided by the conversion continue to work in v15 and > possibly v16? I have the following error that’s being flagged during a > compiler syntax check… Specifically: > > _o_FIRST SUBRECORD([Plant_IU]) //Error: Did not expect a table > > Is there a way to continue in compatibility mode? Why am I getting the error > above? > > Is there a detailed tech-note that maps out the migration path from a v14R3 > or later database approach? > > Thanks, > > Robert ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
