>Greetings!
>
>I've been asked to replace an existing Clipper-based db app with a newer, Windows/VB-based version. The old app used dbf files for its back-end database.
>
>Would it be better if I also "upgrade" the dbf files with an mdb file? I'll be using ADO and ODBC for the connection to a server-located database, where the database file sizes reaches upwards of 100mb per year (annual archiving and extraction prevents further ballooning of the files...)
>
>So in short, do I go with Access mdb, or stay with dbf? Which is better performance-wise for this setup?

Moving to an MDB would be a downgrade of capability and capacities; if you want to migrate away from DBF/DBC functionality, I'd investigate MSDE, which offers a very direct upgrade path to SQL Server in the event that the extra capacities and capabilities are required later. MDBs are just an easy way to hurt both performance and data integrity.