You should use 'Microsoft OLE DB Driver 19 for SQL Server' which you can download from here:

https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16

The bitness of the installer refers to the bitness of Windows, not your application. The 64-bit installer will install 32-bit and 64-bit versions of the driver.

Connection info:

sqlca.DBMS = "MSO"
sqlca.LogId = "userid"
sqlca.LogPass = "password"
sqlca.ServerName = "theservername"
sqlca.DBParm = "Provider='MSOLEDBSQL19',Database='thedatabase'"

Hi Tim,

We have upgraded the ADO driver in PB2022R2. After the upgrade, the default SSL parameters of the new driver may differ from the old one.

Please try configuring the connection parameter: Trust server certificate=true.

You can test the connection configuration in the Database Painter.

If you still encounter issues, we recommend submitting a ticket to expedite the resolution of your problem.

Regards,

Angie

Hi Angie,

That did not resolve my issue.  When I went into PB to test the connection using the Database Painter, I noticed something different.  For the ADO Microsoft ADO.NET option, I was not able to select the Namespace connect information.  I have attached 2 pictures.  One shows the Database Profile Setup from a co-worker who has not performed any of the latest updates for PB 22.  The second shows my options after I performed the latest PB22 updates.

Any thoughts?

Thank you.

Tim

Hi Chris,

Thank you for that information.  I will keep that in mind when we perform our next release.

I was wondering if the option to use the ADO.NET Namespace connection was removed from the latest update of PB22?  Just confused why I do not have that option any more.

Thank you.

Tim

Hi Tim;

  If you are referring to Microsoft SQL Server, then I would drop using the ADO.Net client connection altogether.  ADO.net has always been troublesome for any App (never mind PB). Also, you are then dependent the App user's machines to have the correct .NET installation installed as well. A PIA IMHO.

   => MS now recommends (for quite a few years now) to use the newer MSO client to connect with newer SS versions (and higher).  In your PB App that would be ...

SQLCA.DBMS = "MSO"

Food for thought. 

Regards .. Chris

I was able to connect to the database through the PB Database and through the application using the connection parameters:

What I have noticed is that the driver does not seem to act properly when I choose to connect using SQL Authentication or Windows Authentication.  When I select Windows Authentication, the setting does not seem to be saved when I go back into the properties settings.  When I select SQL Authentication, I enter the SQL User Name and password but when I look at Activity Manager on the SQL DB Server, it shows me connected using my Windows Authentication user name.

Is there an issue with this driver and connecting to the database using SQL Authentication?