Hi Peter,

>After all, it seems to me, all I'm doing is to state explicitly, what is already implied.
>

Sorry, but what you are doing is very different from what is implied. Keep reading.

>Having spent hours trying to address this issue, I'm not in a particularly good mood, but all the same, I don't feel I'm being overly critical in saying, that it's erratic behaviour like this, that makes one wonder, whether it is sensible to keep on developing in VFP.
>

This behavior is not erratic, it is very much predictable. Every change in code has its consequences. In this particular case, every command like 'USE View IN 0' allocates its own connection handle whereas 'USE View IN 0 CONNSTRING lnSql' uses connection handle lnSql. When you run the code, the second view tries to use lnSql connection handle, but the first view is still using it. So, it is expected to have this kind of problem unless FetchSize for the first view is big enough to fetch all records at once.


>In my humble opinion, showing all the code that's going to run, in the View Designers "View SQL" option, would be a tremendous help.
>

I am not sure I understand what you are trying to say. Doesn't View Designer in VFP8 show all the code?

Thanks,
Aleksey.