FORM or FORMM on 5.6 for Windows

[Nancy Palmquist]

I have encountered a strange error - Normal Microsoft Windows kind of error
that wants to send a report to Microsoft.  You know what I mean so I have
no real filePro error but it crashes none the less.

Here is the logic:

input processing had 2 forms that can be printed, each uses @key to start

@keyF	- chain "ch_combined"

@keyO   - chain "ch_orderform"

Within the chained process it does logic and then uses formm "combine", and/or form "combine" to 
print.  When it is done, it chains back to the input table.

Likewise, the other process does logic and then uses formm "orderform" and/or form "orderform" to 
print.  When it is done, it chains back to the input table.

formm is used when I have to print two copies of the form with some minor variations, and actually
that seems to be when the crash occurs.  I always issue first a formm for copy one and then form for 
copy two. If I do not need two copies, it seems to work just fine.

If I go to a record and press F or O - it works perfectly.
If I go to another record and press F or O it continues to work perfectly.

However,  If I sit on one record that will require two copies (A formm and then a form command) and 
press O and when it is finished I press F which will also need two copies, it will crash each and 
every time in the second chain with the FORMM command. (commented out the FORMM command and then it 
crashed at FORM.)

The processes are very similar and the only really significant difference is the form name.

I tried using FORM instead of FORMM, no difference. (It will generate two print jobs and the paper 
could get separated by other jobs, so I really want to stick with FORMM.

I tried using the form name that seems to work always "orderform", and it still fails at that command.

I used the debugger and it always crashes at the FORM(M) command in same chain table.  If I run the 
forms in the opposite order, they work just fine.

WORKS:(2 copies from @keyf and then 2 copies from @keyO)
FAILS:(2 copies from @keyO and then 2 copies frm @keyF)
works: (1 copy from each in any order)

I tried starting the chain tables with PRINTER FLUSH to make sure all prior printing was flushed. 
Still Failed in the same situations.

I can not think of anything else.  It seems related to the FORMM command (when I do not use it in 
any chain, it seems to work correctly.)

Got any ideas out there.  It is really bugging me.

Nancy


-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com