What really makes me smile (or maybe it's just the high-octane coffee kicking in!) is that in a few years or so, the next wave of programmers will say the same thing about .Net/C#/VB/VFP! "I can't believe I'm stuck re-writing this OOP(!) app. What were they thinking!" Now where's that Yogi Berra guy when you need him for a good malaprop. Probably too busy talking to AFLAC ducks... "Deja vu all over again?"
---J

>I'm smiling while I type this because this is the same situation I am in. I am working on a system that took 10 years of development by numerous developers and the data is often handled the same way. With so many developers working on the system over a period of years, there is no standard in it. It is a FPD26 app that I'm converting it to VFP7 and in the process switching to buffering in the process. However, changing from using temporary tables to edit (as well as literally hundreds of arrays used for manipulating data) to buffering is a long process and requires changes in a LOT of areas - not just the data input/edit locations. The app is also written procedural and not OOP so that is a complete rewrite in many cases. This is a very time intensive process and I recommend that you change it to buffering when you can, but if it works well as is, leave it be. The labor to switch it to buffering would have to be justified with a clear benefit either in maintenance or production.
>
>Tracy