Why Won't My .dbf Destination Work
Bradley Schacht is a Principal Program Manager on the Microsoft Fabric product team based in Saint Augustine, FL. Bradley is a former consultant, trainer, and has coauthored 6 SQL Server and Power BI books, most recently Learn Microsoft Fabric. As a member of the Microsoft Fabric product team, Bradley works directly with customers to solve some of their most complex data problems and helps shape the future of Microsoft Fabric. Bradley gives back to the community through speaking at events such as the SQLBits, Fabric Community Conference, PASS Community Data Summit, SQL Saturdays, Code Camps, and user groups across the country including locally at the Jacksonville SQL Server User Group (JSSUG). He is a contributor on SQLServerCentral.com and blogs on his personal site, BradleySchacht.com.
There are actually three different options for the DBase type that are used: 3, 4 and 5. So after a little digging I decided to try and change that to something other than 5. I changed to 4, but that didn’t work. You may need to not only change that, but remove the Persist Security Info=True 
Next on the Connection tab you need to select the database file name. For this be sure to ONLY select the folder that the .dbf is located in, not the actual file itself. 
Finally, in your source or destination selection the OLE DB Connection Manager and on the table or view you will have a list of all the .dbf files in that directory. Simply select the appropriate file name, and you’re good to go! 
Just as a note, when you enter DBase #, make sure to use roman numerals. If you want DBase 3 it must read DBase III, or DBase 4 as DBase IV. If you put in the number the connection will error out. Also, it depends on your system what DBase needs to be in the extended properties, it will not always be DBase IV.