program "hangs up"
Kenneth Brody
kenbrody at spamcop.net
Tue Oct 7 15:52:56 PDT 2014
On 10/7/2014 5:23 PM, Richard Kreiss wrote:
>
>
>> -----Original Message-----
>> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
>> Sent: Tuesday, October 07, 2014 5:15 PM
>> To: Richard Kreiss; filepro-list at lists.celestial.com
>> Subject: Re: program "hangs up"
>>
>> On 10/7/2014 4:52 PM, Richard Kreiss wrote:
>>> Windows server 2008
>>> filePro 5.7.03.06
>>>
>>> I have an output program which is not working properly.
>>>
>>> At @once the program reads into an array all of the pdf files in the directory
>> web_files. When all of the files are read in, the @once section should end.
>>>
>>> The file name is in the format nnnn_yyyymmdd.pdf
>>>
>>> The main portion of the program checks to see if there is a directory for the
>> nnnn portion of the file name and if not makes the directory. If it exists, the
>> file is copied to a directory TODAY and then moved into the correct NNNN
>> directory.
>>>
>>> Here is my problem:
>>> 1. Program starts and then stops without at the first program line of
>>> @once
>>
>> You seems to be missing some word(s) in the above sentence.
>>
>>> 2. If run with the debugger, as lone an enter is pressed the program lines in
>> @once execute.
>>> 3. When the program hits the END of the @once processing, the program
>> stops.
>>
>> When you say "the program stops", do you mean it freezes, without ever
>> hitting output processing, or do you mean it "stops" in the sense that it
>> successfully finishes?
>>
>>> Batch file command line
>>> %pfprog%\fp\dreport library -f move_pdf -y !! -s one -u
>>
>> What's in selection set "one"?
>>
>>> The array dim getfiles(5000)(20,*).
>>>
>>> I adjusted the array to 900 elements as I thought this might be the
>> problem. It isn't.
>>>
>>> Yes, I could rewrite the program to post the files one at a time rather than
>> reading them into an array.
>>>
>>> But that doesn't answer the question of why the program stops before
>> executing any code in @once unless the debugger is on.
>>
>> What makes you think it doesn't execute any @once code when not in the
>> debugger? Does the code interact with the user in any way?
>>
>> If you put a MESGBOX at the start and end of @ONCE, are they executed?
>
> The first thing I did was add show "Files Counted"<ct to show the progress of getting the file names. When the program was run, it never displayed this show statement.
Add VIDEO SYNC. I'm pretty sure you'll see that the code is, in fact, running.
> If I add -db to the command line, the program starts but does nothing. At this point not even pressing enter or q has any effect.
>
> If I add debug on at the start of the @once processing I can walk through the program by pressing enter or setting a break condition after the first file is read in.
Strange that DEBUG ON works, but "-db" does not.
> As there are currently 3041 files in the directory, when I set the break condition to ct="3039" the program loops through quickly and then turns on the debugger. I step through 3 more cycles. On the third round the program hits the end statement and just stays there. It never gets to the main section of the program to process the file names in the array.
Which is probably what's happening even w/o the debugger. It runs the @ONCE
processing, and then for some as-of-yet-unknown reason, doesn't get any further.
You may want to contact fpsupport and arrange to send them files to demonstrate.
--
Kenneth Brody
More information about the Filepro-list
mailing list