A True Puzzle

[Bruce Easton]

That does sound strange, Nancy.  Since you mentioned -u, I'm assuming 
this is a *report process versus *clerk.  When you run in "normal way", 
would that use a different environment in any way than when you run it 
from debugger?  (I'm thinking of filepro env vars that govern places 
filepro dir is, but also the -t type flags; also maybe env differences 
outside of filepro.  So I'm just wondering if your debug test env is not 
exposing you to the same issue.)

--Bruce

On 6/20/16 1:12 PM, Nancy Palmquist via Filepro-list wrote:
> I have a strange puzzle.
>
> A process that has worked for years on a Windows platform, filepro 
> version 5.0.
>
> When I run it the normal way, it seems to stop before doing anything 
> at the first selected record and just sits there.
>
> If I add -db to the command line, the debugger starts and if I hold 
> down ENTER to step through the records with the debug it runs correctly.
>
> I added a SHOW on the third line so I could watch what happened when 
> DEBUG is not on and the show is never displayed when the process is 
> run normally.
>
> If I hit CONTINUE or QUIT in the debugger, it just hangs where ever I 
> left it in the count down.
>
> The command line has a -u and I double checked it is not a locked 
> record issue.  Also verified by the fact that I can step past the 
> records in the debugger.
>
> I rebuilt indexes - who knows right?
>
> Nothing has changed with regard to the data structure or programming 
> on this for many years.  It prints to a file, so it is not waiting for 
> a printer to be online.
>
> What am I missing?
>
> Nancy
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus