>"" Not just yours. Imagine someone doing a nested scan within a scan, doing a textmerge with function calls embedded, which in turn do their own scan/endscans... (so this is four levels, right?)... using ADO recordsets and VB's string manipulation. OK, the string manipulation may be easier in vb.nyet, but still... ""
>
>
>Dragan...
>
>Do you mean to say you've actually tried it? <g>

Well, only as a mental experiment, based on what I read. I had .net installed on a laptop that I soon had to return, and didn't even have the time to play with it. Just read McNeish's book.

>It's not quite as difficult as you may 'imagine' - as part of learning .NET, I took two of my recent VFP apps and 're-wrote' them, to learn the differences between the tools and to build my own toolset in C#/ADO.NET.
>
>Doing so gives one valuable exposure to the capabilities of the .NET framework, and allowed me to dismiss the '.nyet' from my vocabulary.

I didn't say it can't be done - of course it can. It's more the matter of how many lines of code you have to write to do it. And how readable is that code.

For me, .nyet reads as "dot not yet".