Dear JVP,
>> That would have been the wrong way to solve the problem...
>> Highly doubtful - assuming proper configuation. A properly tuned SQL Server db, with a stored proc, will out perform and will out scale a soluton that relies soley on a Fox dbf as a local data source...
In real life where there may be dozens of PCs running this heavy processing at the same time on a loaded network: the result of your solution will be no surprise to anybody who has ever tried to use a C/S system when multiple heavy reports or other intensive tasks cut in at the server. I cannot imagine why one would even consider imposing a server and network load if it can be avoided so easily.
Which is one of the good things about VFP. There *are* instances where an integral local data system offers advantage- obviously, or MS would not be promising to improve it in dotNET. Other times SP seems better. No problem. VFP developers can use (most) SP, SPT or... um, other
Rele
Vant options if they make most sense. Yes I know that VFP cannot fully utilize some SP, in which (rare) case one would need to consider a workaround that may include using a different tool. But that has no bearing on this example.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1