It's part of the Sage client, and it must be 32-bit.  

thank you! When you say 'Sage client', are you talking about the Sage 300 desktop installation itself? or is this a subset of the Sage 300 desktop install?  Sorry i'm a newbie here.

and does ACE (Office Access database engine) 2007 get installed automatically or is it something you have to go locate, download and install separtely.

It's automatic with the WSSETUP\Setup.exe.

You mentioned it must be 32-bit, but must it be Access 2007?  or can Access database engine 2010, 2013, or even 2016 suffice?  NOTE: I'm testing this theory by installing the latest version and testing, then installing the previous version, etc.

It all has to do with how Sage is making use of that set of components to import/export. I understand the desire to move forward with the technology but it is possible to break something subtle that could take a lot of effort to resolve later on.

in my case, i'm just testing the newer components.  just wondered if anyone else had confirmed that Office Access database engine 2010 or higher worked with Sage 300 or if only the 14 year old version was compatible.

I've never tested that. The challenge is that there might be areas within Sage internals that we don't have access to that are making use of that older engine. So you might test and find you can import/export with no difficulties and then the payroll department discovers, two weeks later, that they can't generate their EFT file for everyone to get paid and nobody thinks to see if the underlying technology that Sage is using to generate that file has been replaced.

That's perhaps over dramatic but not outside the realm of possibility so I just want to warn you.

We don't know. Only Sage development can tell you that. I'm sure they'd love to have the newest tools installed as well.

Thanks. I hear what you are saying. Although using 2007 in the year 2020 doesn't tell me there is much interest in leveraging current tools. They had over a decade to make changes and didn't. Not even an attempt to go to 2010 or 2013. It's embarrassing honestly . I installed a different Sage product the other day and it installed SQL 2000 tools. Unreal. Thank you for the feedback though.