Walter,

I think you hit in the head something important. We have an application in VFP (and FPD) that does a lot of what you call "data munging". It performs ridiculously involved pay calculations in order to comply with the Panama labor laws. While we do not use SQL server at all, we could for data storage, but for the munging or grinding, the local engine is precious.

Alex

>This, my fried, is what we call data munging. Trying to do this in .NET requires much, much more than this as there is no SEEK equivalent (No, you can't use a PK here, since it might have duplicate keys for doublebooking) and also no SET NEAR and SET CARRY on functionality, and you've got to poke arround with collections in ado to search for records and insert records at certain positions.
>
>Also notice that this solution optimizes bandwidth, because only the neccesary data is downloaded from the server. When doing all the processing on the server you'd probably end up with way more data to be downloaded into a cursor.
>
>Walter,