>Ed and Cernal,
>
>VFP can still remain the platform if there are other database reasons to keep VFP. Store the data as far as VFP is concerned as a C(nn) field, where nn is large enough, and use a C++ DLL to do all mathematical calculations on the field.
>

DOH! Thanks, Dave - on time and right on the mark. That was just too simple. We can handle the US National Debt in mils that way. BCD is easy for C++; I've even done classes for it before.

>>Be very glad he started moving his app this afternoon to a platform that did not have this problem 3 years before it killed him! IOW, waiting until it smacks him like a ton of bricks, like the few unfortunates who decided they needed to plan for Y2K just before leaving for the New Year's Eve party, does not seem best. He knows he has a problem. It is not a problem now. We know it will be at some point in the future. Fix it before you lose data and have no breathing room. He needs to research now what platform will give him the options to deal with numbers 3 or 4 orders of magnitude bigger than the VFP currency field. We know the answer is not VFP6, and waiting to see if VFP7 might do it is downright dumb. Find the right way to fix it NOW!