Unassigned variable (OpenInsight 64-bit)
At 08 JAN 2022 05:24:19PM cmeyer wrote:
Just installed a fresh copy of OI10.1 and doing some further testing.
Have an error below:
ENG0010: PR_TIME_SHEET_JMC_EVENTS, line 323. Variable has not been assighned a value.
Here is the debug response:
00321: Rem = Mod(Date(),7) 00322: * If Rem > 5 then 00323: If Rem > 1 then 00324: rem -= 7 00325: endThis works perfectly in OI9.4.6 so this may be a bug in OI10.1 or is "Rem" a reserved word in OI10.1
Any advice would be gratefi]ul.
Chris
At 08 JAN 2022 05:53PM cmeyer wrote:
Just as I suspected, "Rem" apears to be a reserved word. Changed "Rem" to "Rem1" and no debug.
How many more such differences are there between OI9.4.6 and OI10.1. My application(s) have more 26 years of development, more than 1,300 forms, 3,683 routines and countless lines of code. Before I go live with my clients, testing is a mamoth task.
Did get 247 warnings when compiling the commuter module in OI10.1. How can I suppress the warning if an equate statement does NOT end in a "$" sign. These warnings hide any real warnings. This does NOT happen in OI9.4.6
Chris
At 08 JAN 2022 05:54PM Carl Pates wrote:
Rem is indeed a common reserved word in Basic dialects when it's the first word in the line. It was always documented as such in Arev and was fixed for Arev64 compatibility.
Regards
At 08 JAN 2022 06:01PM Carl Pates wrote:
How can I suppress the warning if an equate statement does NOT end in a "$" sign. These warnings hide any real warnings. This does NOT happen in OI9.4.6
IDE Menu, Settings, IDE Settings → Source Code Editor, Editor Interface
Compiler Warnings - set to True for those you want to ignore
Regards
At 08 JAN 2022 06:36PM cmeyer wrote:
Strange, "Rem" does not have a problem in OI9.4.6. Why does the OI10.1 compiler NOT give an error or warning when the error goes into debug at run time.
I have changed the "Rem" I found (36 ocurrences) to "Rem1" in Oi9.4.6 and ready to perform another 5 migrations for the different accounts (another 1.5 hours).
Chris
At 09 JAN 2022 03:08PM D Harmacek wrote:
I remember having a similar problem for the migration from Arev DOS to Arev32.
I had been using PRINT: as a gosub label without a problem.
Had to change all of them to PRINT1:
Dave Harmacek - Harmacek Database Systems - near Boston, MA USA