Subject Re: Remote access to a dBase database living on a private server from From Gaetano <gaetanodd@hotmail.com> Date Wed, 9 Dec 2020 08:47:45 +1000 Newsgroups dbase.getting-started On 09/12/2020 03:45, Franck wrote: > Oh and I almost forgot - if I am going to link it to another SQL db, anyone knows which one integrates better? > > MySQL? Mariadb? Postgres? Requirements allow for any of those, the main requirements as to which one I will connect to at the other end will actually be how well it integrates with the dBase module. > > Franck! > Can you specify the dBase table level for those DBF? A majority of people posting here use either MariaDB/MySQL or Firebird. Firebird is a fork of Interbase and Interbase was acquired by Borland in 1991, it used to ship with dBase as an "upscale option for large databases" because dBase is too slow for very large volume. If you are restricted to the 3 options you mentioned, my vote goes to MariaDB, you will find more expertise about it here, should you have questions along the way. What you will probably need to give some attention to is date fields, those are always the catch when working with data between two different database engines. The underlying data for dates in dBase is numeric and represents the number of milliseconds since 1st Jan 1970 (negative numbers reflect dates prior to that date). I have no idea how that reflects when reading dBase files through ODBC. I tried to read dBase7 files with MS Access 365, but the ODBC driver only goes up to dBase 5 tables and Access says the table is not in the expected format... The main new feature in DBF7 vs previous versions is the autoincrement field type. I tried to open a table that doesn't have that field type, but no luck there either.