>Hi Fabio,
>
>>The dogma:
>>If a developer open 100 workareas is not VFP slow,
>>but the developer is incapable, surely .
>>We can do anything with max 10 workareas !
>
>
>Well then classify me as incapable. I've got one or two forms that might contain 100 occupied workareas. Remember that if you're using local SQL views, you'll have one workarea for the view and one for each underlying table, rappidly increasing the number of workareas when opening more view.
>
>In another instance, I've got a query designer that *might* generate a cursor for each column that is requested. If the users have a very complex query, the number of workareas might increase rapidly. It was exactly in this query designer where I spotted the problem. It was taking too much time to construct a result cursor out of several others as I found justifyable based on the code and number of iterations.
>
>To be honest. I'd be seriously crippled with only 10 workareas. I've got queries that on their own already open 10 workareas.
>
>Walter,

Hi Walter,

Of course i Agree.
Which sense has, to be able to allot 32XXX workareas for datasession,
if allotting 10000 the program slows down of 500 times the performances?

But every time i write that a developer environment have various issues when a developer uses many resources,
someone write:
"Hey, you are incapable,
you have not necessary of these resources,
you can do the job with a little fraction of these"

Fabio