Hi Doug...

Sounds like a cool app.

I would take a different approach. Instead of being data down to a local cursor, I would create a VFP COM component that resides on the server that could be invoked via DCOM or remote automation. That COM server could use it's own local cursors to grab data from SQL, munge and do the analysis on the server. If need by, the resulting cursor could be thrown into an ADO recordset, and passed to the client.

Some time ago, I benchmarked indexing operations on server tables. The table was 150 mb's in size. The first scenario involved opening the table from a workstation. Indexing took about 10 minutes. The second scenario involved doing the indexing from a COM server on the server invoked with remote automation. Total time: 40 seconds....


>The company helps folks reduce their debt load. To do that requires a massive amount of data analysis, examining all combinations and iterations of payoff scenarios (hence my recursion question *g*). Currently the data are stored in DBF files on the server where they are open to being compromised. Things like SSNs, credit card #s etc.. All of this will absolutely be stashed (and encrypted) in a SQL table. OTOH, when the analysis is performed on these credit cards, interest rates, payoff times, etc I most definitely want a local cursor to "mung" (as you say *g*) the data.
>