• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • ODBC Driver 17 for SQL Server problems with updating datawindow

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved ODBC Driver 17 for SQL Server problems with updating datawindow

  1. Issue
0
Votes
Undo
  1. Chad Bailey
    Chad Bailey
  2. PowerBuilder
  3. Thursday, 31 January 2019 20:25 PM UTC

I need the ODBC Driver for SQL Server so I can use encryption TLS 1.2.  I've encountered two problems with inserting and updating datawindows. 

I have tables and columns where there is a column on a table that cannot be null but has a database default.  With native client, when a datawindow column has a item status of Notmodified! that column is not included in the insert statement.  With this driver it is included in the insert statement with a value of null, which negates the database column default and triggers an error stating that the column does not allow null values.

The other problem is in the sqlpreview event.  The sqlsyntax variable never shows values for retrieval arguments and update/insert values.  All appear as "?".  This makes it difficult to debug among other problems.

What am I missing?  

  1. DataWindow
  2. ODBC
  3. SQL Server
  4. TLS/SSL
Print Problems after 2017 R2 Migration
QR Code as bitmap in Datawindow
Responses (2)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 31 January 2019 20:45 PM UTC
  2. PowerBuilder
  3. # 1

The question marks could be due to the DisableBind dbparm setting.

Comment
Chad Bailey
  1. Chad Bailey
  2. Thursday, 31 January 2019 22:25 PM UTC
The DisableBind setting didn't make a difference.
  1. Helpful
There are no comments made yet.
Chad Bailey
Chad Bailey Accepted Answer Pending Moderation
  1. Monday, 4 February 2019 19:59 PM UTC
  2. PowerBuilder
  3. # 2

I setup an ADO Microsoft ADO .NET profile, and still using the ODBC driver by stating System.Data.Odbc Namespace with the same Data Source I defined in the ODBC Datasources earlier.  It behaves as expected now and uses the TLS 1.2 encryption.  Problem solved.

Comment
Roland Smith
  1. Roland Smith
  2. Monday, 4 February 2019 20:08 PM UTC
You should report your experience as a bug so they can update the ODBC interface to work properly with the new SQL Server driver.
  1. Helpful
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.