>I still think VFP Rocks and I am going to miss it sorely as it fades into oblivion. But then for most of what I do (data file cleanup, data/field standardization and preparation for mailing) I still have not found a good alternative to VFP. I have major utilities and applications that I have written in VFP for this type of work, but I still spend a good deal of my time at the command prompt tweaking things in the data files to get them just right. Doing the work with just SQL would be a pain and last I looked I couldn't even find the command prompt in Access.<g> I may end up having to go back to dBase.

This is a bit down the road for me... but I've been thinking a bit about my VFP apps ever since I wrote this. VFP still makes the most sense to me for the custom DP work, and also for most of my custom cleanup utility code. Although I could leave my DP front ends in VFP, I would love to be able to move them over to .Net

Just one problem that I can see... I need to be able to browse large datasets and I have a feeling that .Net is going to balk at me loading a 1 or 2 gig dataset. I DO NOT WANT TO USE PAGED BROWSING! I have one rather clunky solution of using a VFP form in my dot net app, but it has a lot of draw backs in it's implementation.

Anyone have any experience with this or any solutions other than paging for it?

Or is .Net already doing this and I just don't know about it?