Extremely bizarre SQL 2005 -> datawindow problem

[cjstjohn]

If anyone could provide some assistance with this, I would be very appreciative.

In the attached file, there is a SQL database backup. Restore this database to a SQL 2000 server and also to a separate SQL 2005 folder. Then, run the PowerBuilder 11 datawindow test application, and supply the server and database name. The datawindow has three columns, and if you execute the program against the SQL 2000 copy of the test database, all three columns show up in the datawindow. However, if you run the program against the SQL 2005 copy of the test database, the third column (alert_text) does not show up.

My colleague believes that this is a problem with the PowerBuilder SQL Native Client driver. I wonder if any of you have encountered something like this before.

 

[cjstjohn]

Nevermind, I figured it out.

The field having problems was a field of type [text] in SQL.

My datawindow, created by selecting fields from a SQL 2000 database, defined this text field as type=char(4099). I created a new datawindow using a SQL 2005 database as the source, and it defined the field as type=char(32766).

Replacing the column type definition in the non-functional datawindow with type=char(32766) has made the datawindow function with the SQL 2005 database.

Kinda weird, though...

 

[mbalent]

Your colleague is correct regarding the SQL native driver.

Matt

"Nature forges everything on the anvil of time