>Is this a legacy situation that you can't change?

Actually, my primary directive IS to change the legacy system into VFP. Unfortunately, that doesn't happen overnight and we have to be able to use the data in the meantime.

I was converting the old app a 'piece-at-a-time' but now it looks like it's going to have to be an all-or-nothing kind of conversion. At the very least, I need to implement a new account number schema.

LM

>>Still, I'm stuck dealing with this issue. Is there any way I can force precision to 16 digits?
>
>
>There was an article in FPA a few months back that described functions for dealing with very large numbers mathematically, but it involved storing and manipulating the numbers as strings. I think you might be out of luck trying to store numbers this large in tables.
>
>Is this a legacy situation that you can't change?