interesting problem

Kenneth Brody kenbrody at spamcop.net
Thu Jun 17 09:10:23 PDT 2010


On 6/17/2010 10:59 AM, Richard Kreiss wrote:
> Declare run_date(8,yymd),filename

So far, so good.

> d_code(4,#)(real field)

That's not valid filePro code.

> Run_date=@td

I would suggest @T4, though @TD is fine with a valid PFCMARK setting.

> Filename="f:\foobar\d_code{run_date{".txt"{""

That's not a valid line.  Please give the actual line.

> System run rreport members -f weekly_report -v sel_members -rw d_code -p
> filename

Again, that's not valid code.  Please give the actual line.

> Filename should resolve into NNNN_20100617.txt for this report.

"Should", or "did"?

> These txt file are being converted to pdf file through Printwiz service.

Via what command?

> There are 130 separate d_codes to select with varying number of member
> associated with that code.
>
> Of these, about 6 files had the name NNNN_201006170001.pdf.
>
> Can anyone suggest where the 00001 after the run_date may have come from?

Give us the actual code to generate the SYSTEM dreport command and all of 
its components, as well as the command to convert the txt to pdf.  Plus, 
what was the corresponding txt filename?

-- 
Kenneth Brody


More information about the Filepro-list mailing list