>Anyone have a possible idea to the following?
>
>FPW26a, WFW3.11
>
>Database are open. All relations set. The user selects the PRINT Button from the main menu. A simple screen opens to prompt (2) buttons appear: "Print current bill", "Print all clean bills".
>
>The use selects "Print current bill". The VALID triggers:
>
>DO PrintBill WITH nChoice
>
>PROCEDURE PrintBill
>PARAMETERS nPrintWhat
>
>DO CASE
>CASE nPrintWhat = 1 &&print current bill
> REPORT FORM invoice FOR NEXT 1 TO PRINT NOCONSOLE
>
>CASE nPrintWhat = 2 &&print all clean bills
> REPORT FORM invoice FOR Invoice.Clean TO PRINT NOCONSOLE
>ENDCASE
>
>The first choice works great, the current bill is printed and life goes on. The second choice produces an Internal Consistency Error.
>
>Nothing changes in the environment, you can start the app print all and ICE, or you can start the app print the current record (great, fine) then print all and ICE.
>
>All the tags have been deleted and rebuilt why does the same form in the same environment with the same databases crash out?
>
>Open for suggestions! and Thanks

Ricky

Is ' FOR Invoice.Clean' really a valid For clause? Does not really look like a valid expression from where I am sitting.

Tom