Mike's suggestions are the best.
But if you want to use Excel.....
Some 'tricks' about saving an Excel file as a DBF.
1. Make your top row, a row of field names (limited to 10 characters with no spaces).
2. Highlight/Select all rows & columns that you want to export, but NO other rows or columns.
3. Make each Text column slightly wider than Auto-fit makes it, so as to prevent en-expected field value truncation
4. Even though Excel column data is set as Text, if the data appears like numbers, Excel will export it as numbers.
If you want that column to be characters, insert a row below the top (field name) row and insert a character above the numbers. This 'dummy' row can be deleted later.
5. Remember that Excel is limited in the number of rows that it can handle. If your text file is too large, Excel will chop off the rows that it cannot handle.
6. Also note that the steps that you currently use above can all be automated as a process within VFP.
You do not tell us if this is a one-time import or if this has to be done repeatly.
If one-time any of these suggestions will work.
If repeatedly, then you may want to consider automating the process in VFP with one of Mike's suggestions, or VFP automation of your existing procedure or even low-level operations (FOPEN(),FGET(),etc.).
Good Luck,
JRB-Bldr