JVP:Excuse me. But was'nt you that trotted how bad it would be to revert to using Do...While , since Scan...EndScan does not work with ADO Recordsets. I mean, you did post that ....did'nt you???

JR:No John. I did not say that. You pretended I did so that you could "correct" the point I never made. Perhaps you should go back and read the post again. This is what "straw man" means.

John, the thing I love about on-line forums is that there is a trail
of posts. So, when folks deny things that are said , well, there is a permanent record. So, please comment on the following - as it is in your own words:

Your post of 6/10 at 2:18:48 PM:

**********************************************************************

Progressive? With FP2.0 we moved *away* from DO WHILE loops to SCAN for database iterations, because SCAN was optimised and worked better. Now we "progress" back to DO WHILE loops using ADO.

You will understand why some FP people might have an issue with this- if ADO is based on FP, then it is *very* fair to wonder why we are reverting to constructs abandoned in FP years ago.

Finally, If you could just reassure me that ADO allows expressions and functions in the DO WHILE statement, as well as memory/object scatters etc that make VFP database development so productive, then that would be a big help.

***************************************************************************

Yes, I put code to your example, but it was you that trotted out that ADO is a step backward because you cannot use Scan...Endscan. I am well on record saying that giving up Scan..Endscan for ADO is no big deal. I was discussing this issue with Gene Berger. Don't go up here and deny what you wrote that it would be step backward to use ADO because Scan...EndScan would be lost. It just shows that you are not looking at the bigger picture. Whats worse, it shows that you don't stand by what you write.

FWIW, FP never abandoned the Do...While Construct. I meant to comment on this much earlier.