Hi Fabio,

The help file clearly states that this command doesn't change work area and that the way it always worked. If workarea changed after INSERT INTO command than it's a bug. It's irrelevant if table was open already or INSERT INTO command opened it and where it has been opened.

>Infact i have not see this until now.
>
>But my perplexity is this:
>it is a bug ?
>
>I explain:
>

>SELECT 0  && workarea is 75
>INSERT INTO myTable (...) SELECT ... FROM ... myFunction() ... && this can use WA 75
>? myTable2.fieldname && if VFP return to 75 it is not deterministic
>
> myFunction
>USE ... IN 0 ALIAS myTable2  && this can use WA 75 or 76 or ...
>

>then because the free workareas are used by VFP Engine and by VFP program,
>result can to be not deterministic.
>
>Only one hypothesis in order to explain this modification or bug of VFP8.
>
>However, if it is by design then it is a document bug.
>