@menu in clerk form behavior

[Bruce Easton]

Interesting.  The value of @td is known and can be displayed during 
@menu, but there doesn't seem to be any way to get it on the form.  
Without real fields nor even system fields that have nothing to do with 
a specific record, I'm surprised that the form command is even legal or 
produces anything at all from that trigger, but it will output the form 
(just text that is on the form).  I was testing using 5.0.14, and also 
tried assigning the value of @td to a global dummy field.

Bruce

On 8/23/12 10:39 AM, Scott Walker wrote:
> >From the fp manual:
>
> @menu processing is performed while the user is standing on record 0. There
> are no real fields available.
>
>> -----Original Message-----
>> From: filepro-list-
>> bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
>> [mailto:filepro-list-
>> bounces+scottwalker=ramsystemscorp.com at lists.celestial.com] On Behalf Of
>> Scott Nelson
>> Sent: Thursday, August 23, 2012 10:24 AM
>> To: Filepro-list at lists.celestial.com
>> Subject: @menu in clerk form behavior
>>
>> I have an script that runs a fp process using a clerk to a virtual file
>> with @menu to start the processing in the input table.  After adding a
>> form command to print a page with the variables in the table, the form
>> always prints without any variables, including the !@td field.
>>
>> Is this happening since I am not actually sitting on a record, but
>> running the process with @menu?
>>
>> Thanks,
>>
>>
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>