1. Jonathan Miller
  2. PowerBuilder
  3. Monday, 21 January 2019 18:13 PM UTC

We've recently updated one of our internal testing environments to use ODBC Driver 17 for SQL Server to support more recent versions of TLS and have discovered that our application will crash to desktop with an IDMS error in PBSHR170.dll if we SELECT any data from a column of XML data type.  This happens both in the deployed application and in the powerbuilder IDE, in both 2017 R2 and R3. When it happens in the IDE it's a complete crash to desktop for the entire IDE, no error is caught by the debugger.

Has anyone else encountered this and is there any solution other than "don't use the XML data type"?

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 21 January 2019 18:44 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Johnathan;

  Hmm .. IDMS error. Wow, a blast from the past name. Dave Litwack who designed PB came from that products company.   ?

   Yes, XML data would need to be treated as either: a) SS data exposed as a web service via SP's (SS now also supports RESTful web services too) or b) have your PB App use a SelectBlob command & then parse the datum via PB's PBDOM feature.

Regards ... Chris

Comment
  1. Jonathan Miller
  2. Monday, 21 January 2019 18:48 PM UTC
SELECTBLOB was the answer, thanks!



I guess the real "problem" was SELECTing into a string working in the first place with the older ODBC driver. Now we know!
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 21 January 2019 18:55 PM UTC
Excellent news Jonathan ... Happy PB'ing!
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 21 January 2019 18:24 PM UTC
  2. PowerBuilder
  3. # 1

Have you tried connecting with OLE DB? MSOLEDBSQL is the new provider.

Comment
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.