John,

Yes, I use quite a bit of databinding especially with grids and listboxes and so on in .NET, I did as well in foxpro.....( i am familiar to data binding in both and dont see one being harder than the other, just different.)

Well, I'm not to sure that there is any amount of data you plan to bind that is going to take up your entire memory...(can you give me a reference to where you saw that the memory residencey is a known problem with microsoft) and if you're talking about scalability from what I understand ADO.NET is very scalable, especially with its use of the disconnected architecture, and its use of XML.

As for DBF vs. SQL,yes it depends on the company, but the whole 2GB limit can be very annoying. As for me I've been dealing with a lot of data so it makes sense to go to SQL. Which I do think FoxPRo is a great frontend for. But I just dont think this constant donNet thing that oh, its hard, it takes more lines of code, it doesnt have cursors, or its more difficulut to work is plain silly. I have always said "Combine Them", use XML web services with a FoxPro front end! It works very well and tends to be very fast. Most of the time we use a set of web services to connect to the .DBF files which return datasets, variables, strnigs whatever and then databind....we are yet to have a speed or scalability issue.

So, I'm a bit confused by Jordans statements about .NET being hard to create over .DBFs, I'm not sure he meant to connect to, or what, but either way saying .NET is difficult to databind is false as well, is it easier in foxpro...maybe, depends on who you ask. But going back to the scalability issue, I dont think I would choose anything else but ADO.NET, it works great with web services. But that just might be what works for us.