dBase was one of the first database management systems. Visual FoxPro, Clipper, XBase and FoxBase all use dBase's DBF file format for their database files.
We support very fast DBF reading and writing in our products! No drivers are needed as we developed our own highly optimized DBF file technology.
Database file format dBase uses (files with extension .DBF) is well documented, which allowed many 3rd party applications to read and write DBF files. Also, many programming languages/database systems rely on DBF format. xBase is a general term describing all programming languages deriving from original dBase (Ashton-Tate) language and database format. Visual FoxPro is Microsoft’s product, derived from FoxPro (developer by Fox Software back in 1984.) FoxPro was originally named FoxBASE. Clipper was originally a compiler for dBase III (created back in 1985), sold to Computer Associates and renamed as CA-Clipper in 1992. That’s quite a rich history of some very popular products.
Like CSV files (and in smaller measure, Excel documents), DBF files are a de-facto standard for data interchange. When we compare DBF and CSV formats, DBF is superior in several ways:
• DBF is a binary format, so less space is used than in textual CSV format
• DBF tables define column data types specifically
• There are separate memo files that store large textual data, allowing for long multiline text to be stored
We have written our own direct DBF reader and writer components, very efficient and fast, allowing us to both read and write files made by any application conforming to standard DBF structure. There are several versions of DBF format and we can handle all of them.
All our products support DBF database natively. No drivers are needed, you will be able to work with DBF as soon as you run our applications.DBF is also known as dBase, FoxPro, Visual FoxPro. (related files: dbf, ndx, mdx)
It may make sense to migrate your data away from DBF. You may want to do it permanently or just need to share your tables with a collague in a different format.
We will copy all your tables with their data and apply indexing and relationships exactly as they are in your current DBF database. In a nutshell, you get exactly the same database in another database engine. Each time you run the migration, we will copy all the tables again. Of course, we have a built-in scheduler, so you can run this overnight and have a fresh database copy in the morning.
Have a need to import data from various sources into your DBF database? Luckily we support many popular database formats to make this easy for you. Instead of messing with exporting from source, then working your way to somehow import data into DBF, use our tool to copy all desired tables directly - quickly and easily.
If you have already created your target database (by yourself or using our Full Convert product), you can synchronize data in your target database with your original DBF database. We never pollute your databases with additional tables or triggers for replications. We never even write to your source database.
Replication allows you to update your target database very often, as we always write just a minimum of changes needed to bring databases in sync. For example, if you added three records to a single table in your DBF database, our replication product will write those three records to target database and nothing else. If you deleted some records, changed some others and inserted some, again – our product will pick that up and replay those changes in the target databases without touching existing data that should stay there. Our products are highly optimized for real-world workloads, so data that's inserted into different areas of table are combined and written using high-speed algorithms, as available in a specific target database.
You can run database replication often, as your target database is never empty while replication runs. You will simply see that your changes are applied on each run.