>We're having Stack errors when running a large report.
>
>I recently set stacksize to 2000, but that didn't fix this problem.
>
>The VFP docs say you can go up to 64,000 for stacksize.
>
>Is there any reason not to set it to the max?

In many implementations of garbage collected memory time to collect grows with allocated memory.
Tested - Running same vfp code under tiny memory will show different times compared to allocating oodles of mem space - often faster with SQL munging, slower with often running sys(1104).
Guesstimate: similar effects might exist with stacksize