Hi Sverre

  Yes, the "MSOLEDBSQL" DB Client is now Microsoft's current recommended SS connectivity mechanism - especially going forward. There are still DB connecti0on alternatives like ODBC for example that you can use but for SS 2022, both the OLEDB and SNC DB client drivers are now deprecated by MS.

  If you stay in the Client / Server paradigm then yes, you will still need to install the appropriate SS DB Client software. That is no change from what you have been doing to deploy C/S Apps with PB releases from PowerSoft, Sybase, SAP and early Appeon PB releases. If you stay in that C/S paradigm  - even in the latest PB 2022 R3 version - you would be required to install the DB client using the same deployment considerations you have been used to.

  However, if you move to the new Native Cloud paradigm (aka PowerServer feature), then the data access and all related SS connectivity software to be installed and run is handled in the middle tier as your PB Apps are now processing as an N-Tier PB applications.

FYI: https://www.appeon.com/products/powerserver

  PowerServer Native Cloud apps are still native PB App execution. Its just that the App delivery (including the PB runtime) is via a Web Server. Once the PB App is delivered to the App user from the Web Server, the PS App then connects to PowerServer (middle tier) where all the SS Data interactions are processed.  Food for thought

Regards .. Chris

all versions of windows (not sure about 11, but it runs on my new windows 11 laptop) from vista (i believe) came with oledb installed (old/original oledb not the msoledb).  That is still an available option for powerbuilder. 

If you are not using any of the newer features in sql server then maybe that is an option.

You stated "32bit apps" but then ask about x64?  you need to install same bitness 

Right . But up to and including PB 2022, the appropriate client drivers for ADO.NET could be bundled together with the rest of the PB runtime components and copied from a file server to each client machine by the same script. That has been our deployment mechanism for fifteen years now. Now we need an installer executing with AD admin permissions due to ever increasing security policy. I suppose that can be done with Group Policy tools.

Thanks for clarifying!

regards sverre

mike,

yes that is the only option if one wants to avoid the client machine installer problem. As to bitness, the 64 bit installer is intended to match the OS , and supports both 32 & 64 bit PB applications.

cheers

sverre