SYMPTOMS
When you create a Microsoft Office Access table that contains long integer
numbers and then you export that table as type dBase IV (.dbf), the numbers are
converted to
double data type and will show decimal places.
For example,
you may export the following table:
UNITS
23411
111111111
1121212
When you then import and view the data in dBase IV, the
data appears similar to the following:
UNITS
23411.00000
111111111.00000
1121212.00000
Note When you create a number field in a table in Access, you use the
FieldSize property to control the amount of space that is allocated for a
particular field. For number fields, you can choose one of the following numeric types from a list:
- Byte
- Integer
- Long Integer
- Single
- Double
- ReplicationID
- Decimal
By default, the setting for number fields is Long Integer. The Long
Integer value stores whole numbers that range from about -2 billion to +2 billion.
Or, you can choose the Double value to store numbers with decimals.
WORKAROUND
To work around this problem, use one of the following methods:
Method 1: Modify the database file in dBase
Modify the design of the database file after it has been added to
the dBase catalog. For example, set the Dec column to 0 (zero). For additional
information about designing database files in dBase, see the dBase
documentation.
Method 2: Use Microsoft Office Excel to format the data
Use Excel to format the data in the table that you
exported. To do this, follow these steps:
- In Excel, open the table that you exported as type dBase
IV (*.dbf) from Access.
- Format the cells that are not correctly formatted. To do
this, select the cells, and then click Cells on the
Format menu.
- After you have formatted the cells, export the spreadsheet
as a dBase IV file. To do this, follow these steps:
- On the File
menu, click Save As.
- In the Save as
type box, click DBF 4 (dbase IV) (*.dbf), and then click Save.
Method 3: Use sample code to format the data
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. You can use the following code sample to automate
the process of formatting the data. The sample will save a table as a text
file. Then, it will automate Excel to open the text file and then save it in dBase IV
format.
Note You must change the file names in this code sample to match your
file names.
Sub exportFormat()
Dim xlApp As Excel.Application
Dim xlBook As Excel.Workbook
Const SAVETEXT = "C:\testValues.txt"
Const SAVEDBF = "C:\testDBF.dbf"
' Save the table as a text file.
DoCmd.TransferText acExportDelim, , "Table1", SAVETEXT, True
' Set a reference to the Application object.
Set xlApp = CreateObject("Excel.Application")
' Set a reference to the Workbook object.
Set xlBook = xlApp.Workbooks.Open(SAVETEXT, , , 2)
' Save the file to dBase IV format.
xlBook.SaveAs Filename:=SAVEDBF, FileFormat:=xlDBF4
xlBook.Close savechanges:=False
xlApp.Quit
Set xlBook = Nothing
Set xlApp = Nothing
End Sub