>There are a lot of factors to consider! My competitors seem to be using a large ASCII file in a non-database format. Maintainence must be terrible! But somehow they know how to find the data in that monster.
>
>The calcs seem to me to be simple enough in most cases- 3 to four values from different tables with an algebraic operator.
>
>I've heard of a 3rd party called CodeBase? that allows C to directly access DBFs and that may help with your suggestion of dropping down to C from within Foxpro.
>
Just a note on Codebase...I used this a couple years ago, and don't recommend it, unless it has dramatically improved...you might as well just program in foxpro, unless there really is a serious speed issue...it kind of takes the worst of both C and foxpro and blends them together (massive C declarations, lots of calling functions, not great speed...) At least that's my memory of it.(s)

I also note that at the time, I was trying to expedite a foxpro pgm that was taking about 10 hours to run (someone else programmed it). I redid in foxpro and cut the run time down to less than an hour, testing run times with different techniques on each step as I went through the process...