Our app is in the mutual fund industry and is VFP and SQL server backend. We do huge amounts of data processing mostly in cursors on the local box after pulling data from sql server. We process upwards of millions of records at a time. You can't do this easily in SQL server, so we are looking at how to refactor our processes to utilize the server to return the data we need instead of doing it on the local machine. We are moving the app to c# from VFP and over the next year or so we'll have an operational .net program.

So far we haven't had to much trouble and it seems to be working nicely. We have yet to test it with 100K records or more, so I can't tell you about that yet.


>This too is our problem. We are the only solution in our industry niche, but very uniformed IT guys are pushing for us to move to a SQL back-end and they control someof the purse strings for our clientele. So over the next couple years we move to SQL and while we are at it start a re-design in C# and slowly move chunks over until its all .NET stuff.