It is probably good practice to assign the result to a different variable to the variable you are changing.
At machine level you are updating the registers you are reading. This has led to many inconsistent behaviours over the years and probable bugs into the future too. Appreciate it is annoying and a lot of code adjustments David Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: [email protected] <[email protected]> on behalf of Clifford Ponce <[email protected]> Sent: Friday, December 30, 2022 6:16:35 AM To: jBASE <[email protected]> Subject: Re: ICONV Broken on 5.8 Here is the latest response from Rocket: The problem here is now with ICONV, but with the jBASE runtime. There is a known problem where, in the left side of the argument you cannot store the result of the function used with the variable on the right side of the argument. Change your code to read: AMT = REC<4> + 0 NEW.AMT = ICONV(AMT,'MR2') CRT "AMT = " : NEW.AMT A<X> = NEW.AMT Um, holy crap! What!? That is kind of the WHOLE idea of a function!!! Sure hope this gets resolved soon. On Thursday, December 15, 2022 at 4:10:05 PM UTC-5 Rick Weiser wrote: Sorry, I see that Robert is on the email. What is Rocket doing about the issue? On Thursday, December 15, 2022 at 4:09:03 PM UTC-5 Rick Weiser wrote: Hi Cliff, Why aren't you opening a support call with Rocket? Rick On Saturday, December 10, 2022 at 12:13:40 AM UTC-5 [email protected] wrote: We recently upgrade from JBase 5.2 to JBase 5.8 (Minor 6.5, Patch d08c917, Change 25023) We have discovered that ICONV DOES NOT WORK under several circumstances. We have been unable to make simple test cases as ICONV does work sometimes and seems to work in our test case attempts. Robert Burke from Rocket (Zumasys) has been on our system and witnessed the troublesome behavior of this very important and primary function. It has caused major problems with our system. It has effected our inventory to the tune of hundreds of thousands of dollars and we have spent hundreds of man hours fixing data and creating programming work arounds. Has anyone else experienced this. I caution everyone to not upgrade until they can guarantee this issue is resolved. -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jbase/30b48234-1d80-46c7-b734-0e6c8e47f73dn%40googlegroups.com<https://groups.google.com/d/msgid/jbase/30b48234-1d80-46c7-b734-0e6c8e47f73dn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jbase/SY4PR01MB823207FA903ABF3111078D23F9F39%40SY4PR01MB8232.ausprd01.prod.outlook.com.
