External component as thrown an exception

Hi Rich - no, the latest communication with support was late last week.  Feb 27/28th - or so.   The case is still under investation - with no known solution date.

I did attempt to go down the ODBC route on desktop PBI - and does seem to be working better.   However, with occassional hiccups.   I then ventured to attempt the import process using ODBC connector within the Service dataflow, and in my simple testing case-no refresh failures.

Thanks for your suggestion on linking files.   However, I am a "greenie" in this stuff -and my research didn't get me very far.  But, yes, linking files would be a solution.   As data is updated, what is the process to 'reload" the date into a linked mdb file.  Is it manual?

What I have are annual mdb files - with potentially 20+ years of data.   But, for now, I am limiting my import to 4 years (files).  But, the challenge - I need two tables within the mdb file, thus doubling the import queries.   With the older "folder" connector - the process was straight forward.   I have 3 differing sets of annual mdb files to deal with.  (3 sets*x2tables x 4yrs) = 24 potential queries.

Will keep everyone posted.  I was hoping the tech would get back to me after this weekend's email informing her of my ODBC efforts.