TaDa...and DUH! It was the provider. Changed from "Microsoft.ACE.OLEDB.12.0" to, "Microsoft.Jet.OLEDB.4.0" and all is well.

BTW - I changed all of the other properties back to their defaults and the package still works:

A. Run64BitRuntime=True

B. ProtectionLevel=EncryptSensitiveWithUserKey (even though the package is not getting executed under the same account it was authored with)

I should have went with my gut instincts on this one. Would have saved a lot of time...