1. Brett Weaver
  2. PowerBuilder
  3. Thursday, 18 May 2023 03:44 AM UTC

Hi There

I have been using the new MSOLEDBSQL19 to attach to sql server. I have come across an annoying limitation. My application allows users to define new parts of a document by instantiating a tab page which has a datawindow on it. These pages number around 15 and everything works well. But I have found if we get to 22, SQL Server Complains 



When I change the connection back to Native Client (which is being discontinued) everything works fine.


I'm guessing this is a Microsoft issue, but if there is a configuration option I should be using, I'd love to know about it.

If it is PowerBuilder I am compiling 64 bit, Version 2022 Build 1892





Accepted Answer
Brett Weaver Accepted Answer Pending Moderation
  1. Thursday, 18 May 2023 10:59 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Folk,

Turns out the connections failing were using an old ADO.Net connection, not the MSOLEDBSQL19 driver. Sorry about that - I missed which lines had been commented in the .ini file. . interestingly when I look at my application running in task manager - now successfully -  using the MSOLEDBSQL19 driver it looks like it has created an entry (and possibly connection) for each tab page:

All working now though and apologise again for wasting folks time.

There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Thursday, 18 May 2023 05:11 AM UTC
  2. PowerBuilder
  3. # 1

Hi, Brett - 

Interesting. Is a new Transaction object being instantiated, initialized and connected when a new tab page/DW is created? If so, why?

Best regards, John

  1. Miguel Leeuwe
  2. Thursday, 18 May 2023 05:12 AM UTC

I was wondering the same thing.

Can you show us your sqlca values when you create a connection to the database?
  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.