Have you tried viewing and printing from the db explorer? That way you can make 
sure the label report did not get corrupt.

Dan Goldberg


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Rich
Sent: Thursday, May 14, 2020 10:50 AM
To: [email protected]
Subject: Re: [RBASE-L] - Strange issue

Tried running it with TRACE still did not work

Sent from my iPhone

> On May 14, 2020, at 11:45 AM, A. Razzak Memon <[email protected]> wrote:
> 
> Rich,
> 
> As you stated the routine worked fine previously, and also in a prior 
> version, and not the current version, there must be a setting change 
> that is causing the routine to not work as expected.
> 
> With TRACE "acts like it works" meaning that the routine works in 
> TRACE mode but not when running the routine, the setting would be WHILEOPT.
> 
> Please review:
> 
> ----------------------------------------------------------------------
> ---- From The Edge.: Understanding WHILE Loop Optimization
> Keywords......: Commands, WHILE, ENDWHILE, TRACE, WHILEOPT
> 
> Have you ever run into a situation where your command file or 
> application does not work correctly, perhaps where a few variables are 
> not being calculated correctly within a WHILE ... ENDWHILE loop, or 
> your applications closes unexpectedly? But, if you run that command 
> file or application in the Trace Debugger it returns no errors, or if 
> you SET WHILEOPT OFF, the routine works as expected. The scenarios are 
> typical symptoms of a non-optimized WHILE loop.
> 
> As a control structure, WHILE loops are always considered one of the 
> faster ways to process code because R:BASE read the WHILE loop code 
> into memory and parses it before beginning execution. R:BASE does not 
> need to do line-by-line reading and parsing of the code for each 
> iteration of the WHILE loop. As it is reads into memory the WHILE loop 
> code is parsed in tokens (4-byte segments). But, R:BASE still needed 
> to figure out what is what (e.g., parse the expressions, find variable 
> names, values etc.). It is faster than reading and parsing line-by-line, but 
> not as fast as it could be.
> 
> In current R:BASE releases WHILE loops have been made much faster. 
> Some of the commands in WHILE loops are optimized as well as parsed 
> when the WHILE loop is read into memory. Optimization means that 
> information about the command is stored in a binary format that can be easily 
> processed.
> 
> Optimized commands and variable names, type, and location are stored 
> as numbers and expressions in binary, which allows faster 
> identification for execution and uses less storage space.
> 
> Complete details and examples are described within the Understanding 
> WHILE Loop Optimization technical document.
> 
> From The Edge: https://www.razzak.com/fte Article Title: Understanding 
> WHILE Loop Optimization
> ----------------------------------------------------------------------
> ----
> 
> Very Best R:egards,
> 
> Razzak.
> 
> https://www.rbase.com
> https://www.facebook.com/rbase
> 
> 
> At 08:36 PM 5/13/2020, Rich wrote:
> 
>> Using the latest version of 10.5h. I have a program that produces labels by 
>> client Program run one per month. Last month it worked fine and has been 
>> working for the last 20 years. Today the labels came out blank with just the 
>> static variables printing. I changed clients and they came out blank too. I 
>> rebooted the server, reloaded the database that did not fix the issue. I 
>> moved the database to a machine that had 7.6 and it worked fine. Any ideas?
> 
> 
> 
> 
> --
> For group guidelines, visit 
> http://www.rbase.com/support/usersgroup_guidelines.php
> --- You received this message because you are subscribed to the Google Groups 
> "RBASE-L" 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/rbase-l/1MMX5X-1jpwtB3oRD-00Jelf%40mrelay.perfora.net.
> 

--
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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/rbase-l/097D581B-8240-4EF4-A237-C3EBBBEC73D3%40ogdengroup.com.

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" 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/rbase-l/2E4830CEC16615458329D3D83342F8D0014E4F6216%40exchange11.

Reply via email to