Ray,
This link might help you: http://support.microsoft.com/kb/230126/EN-US/
I am pretty sure the mystery table os a Paradox table. Borland and Paradox used to be pretty close. Do you own any of the Borland development packages? The reason I ask is because there is a SQL explorer that is budled with Borland (atleast it was bundled with my C++ Builder).

Einar

>I have a set of tables from an unknown database that I need to import into VFP 7. These tables ship with BDE as part of their application and the file extensions are .DBF, .DBT, and .MDX. My immediate assumption was dBase IV, but USE generates a “not a table” message, regardless of SET COMPATIBLE. "SELECT * FROM MysteryTable" also generates “not a table.” "IMPORT FROM MysteryTable TYPE PDOX" (hey, I was desperate) gets me a “Paradox file format is invalid.”
>
>My mama didn’t raise no dummy so I went to ODBC.
>

>nSQLHandle=SQLSTRINGCONNECT("Driver=Microsoft dBase Driver (*.dbf)" + CHR(0) + "DBQ=" + cSrc)

>gets me a connection handle, where cSrc is the data path, but
>

>lnSuccess = SQLEXEC(nSQLHandle, "SELECT * FROM MysteryTable", 'MyCursor')
>

>returns -1 for dBase 3, 4, and 5. No joy in Mudville.
>
>So I fire up Access 2003 and do the File>Import thing with files of type dBase IV, and sure enough, it pulls them right in, no questions asked. So now I could bring them all into Access then from there into VFP, but I’ve got 19 sets of data, and each set has over 300 data files, and I’m too old to deal with all that before I die.
>
>Anybody have any better ideas?