Convet dBase IV to Access 2013

[amerifax]

It took about a year with the help of Microsoft's best support. And also dBase Plus 8 http://www.dbase.com/support.

You will not be able to load your dBase IV files into Access 2013 without the following. Actually, I should say you will be able to load access 2013 but as soon as you try to change the size of a field you will get the memory and file size error message.

This is my cure:

1. Open your DBF file *.dbf inside of dBase Plus 8.
a. Remove your indexes.

2. Save your file.

3. Now use dBase Plus 8's conversion utility.
a. Export your file as an Excel. You have more choices, but I used Excel.

4. Now open your Excel file in access. All works good at this point.

Note: Best way to know that you have a problem or you have fixed your problem is either the appearance or not the appearance of the error message regarding not enough memory or disk space.

Bob

 

[amerifax]

Convet dBase IV to Access 2013
It took about a year with the help of Microsoft's best support. And also dBase Plus 8 http://www.dbase.com/support.

You will not be able to load your dBase IV files into Access 2013 without the following. Actually, I should say you will be able to load access 2013 but as soon as you try to change the size of a field you will get the memory and file size error message.

This is my cure:

1. Open your DBF file *.dbf inside of dBase Plus 8.
a. Remove your indexes.

2. Save your file.

3. Now use dBase Plus 8's conversion utility.
a. Export your file as an Excel. You have more choices, but I used Excel.

4. Now open your Excel file in access. All works good at this point.

Note: Best way to know that you have a problem or you have fixed your problem is either the appearance or not the appearance of the error message regarding not enough memory or disk space.

Bob

 

[Steve R.]

This is a duplicate of your earlier post: import dBase IV to Access 2013. Thanks for providing this work-around, but it would not address your original question of moving your dDase database to MS Access.

Please note the advice provided by Pat Hartman on your other post.

A one-time conversion is a completely different problem from an on-going interface.

As has already been suggested, if you have a one-time interface, import using an older version of Access and be done with it. Once the files are imported, they are no longer dBase and you no longer have a problem.

 

[amerifax]

Thanks for the help. I only wish I would have thought to use an older version months ago. It is a perfect solution.

Bob