interesting problem

[Barry Wiseman]

On 6/17/2010 1:46 PM, Richard Kreiss wrote:
>
>
>> -----Original Message-----
>> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
>> Sent: Thursday, June 17, 2010 12:10 PM
>> To: Richard Kreiss
>> Cc: filepro-list at lists.celestial.com
>> Subject: Re: interesting problem
>>
>> 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. - done
>>
>>> Filename="f:\foobar\d_code{run_date{".txt"{""
>
> OK: here is the code:
>

[snip]

Well, _some_ of the code.  You're not showing us where the value in doc_code comes from, which of course is the crux of the matter.

By turning off printwiz and inspecting the .txt files generated by filepro, you could verify whether the filenames are already wrong (in which case the problem lies in filepro) or still correct (in which case the problem lies in printwiz).