2 Replies Latest reply on Feb 15, 2017 4:10 PM by Jonathan Drummey

    Export worksheet as new data source not working on Mac

    Bobo Wieland

      I have a workbook where I have some aggregated data on a worksheet that I've stored as a new Data Source.


      When saving this I only have the option of saving it as a Microsoft Access Database (.mdb)


      I've exported the workbook as a packaged workbook to let some colleges use it. But the run Tableau Desktop (trial) on Mac. Hence they can't access the .mdb data source.


      How can I fix this?

        • 1. Re: Export worksheet as new data source not working on Mac
          Patrick Van Der Hyde

          Hello Bobo,


          It sounds like you are asking a licensing issue to allow users to access a .mdb file from Tableau Desktop.  These users should contact Tableau via the Contact Us link at the bottom of this page to discuss licensing options with a Tableau Account Manager.



          • 2. Re: Export worksheet as new data source not working on Mac
            Jonathan Drummey

            Hi Patrick,


            I suspect this is a different issue... .mdb files are Microsoft Access databases and Microsoft does not provide a driver for Macs and we don't have a generic ODBC connector on the Mac to use with the few bits of third-party software that can connect to .mdb files.


            Assuming this is the case there are three workarounds:


            1) Create a Tableau data extract of the .mdb file prior to exporting as a Tableau Packaged workbook. Tableau for Mac has no problem reading extracts whatever their source.


            2) The original issue is creating an aggregated source by using Tableau's Export Data function that creates the .mdb. It could be possible to avoid that manual step by using something like Level of Detail expressions or table calculations in Tableau that can be nested on top of regular aggregations (thereby creating aggregates of aggregates). Without knowing more about what's happening in the exported workbook I can't be sure if that's the way to go, so there's one more workaround...


            3) Alternatively to #2, an aggregated data extract could be created and avoid the need for a manual export.