>Thanks much for your continued help, but I'm still not getting my imports to work. I've changed tacks, in that i'm trying now to import my flat ascii
>file into an "intermediate" .dbf file. I copied the destination .dbf file
>and changed the type of field from 'date' to just 'character', thinking
>that foxpro could make the conversion easier if it is going from one
>database to another, rather than from one .dat file directly into a .dbf
>with date fields. I'm also having trouble with my 'currency' fields on
>my destination database not working right. Should I change their data type
>on my intermediate database to numeric instead of currency? Will they then
>make the conversion between my intermediate database and my destination
>database?
>
>Also, what is the correct way to import a memo field with nothing in it? I've got several memo fields in my destination database. How should I define them to my intermediate database?
>
>I have no control over the destination database's characteristics, since it is a table defined as part of SBT (ACCPAC)'s accounting package, and I'm trying to download my mainframe data to it. I do have control over the flat ascii file and the intermediate database, obviously.
>
>Thanks.
>
>Doug Bell

An intermediate DBF is basically what I was talking about. Then you have full control tro adapt structures and masage the data before sending to its final destination. VFP is excellent at data munging.

I don't use currency much. If it gives you heartburn, then use numerics first then swap.