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

Resolved Strange characters in DDDW

  1. How-to
0
Votes
Undo
  1. Colin Cruikshank
    Colin Cruikshank
  2. PowerBuilder
  3. Monday, 4 October 2021 20:27 PM UTC

Hi there,

We recently upgrade from Powerbuilder 2019 R2 to R3, and I wont swear that this is related, but I noticed that one of our drop downs is displaying odd characters instead of the value in the column. So far i've found it only occurs on two rows in the DDDW. Here is an example of what it looks like:

 

 

The expected value is definitely in the DDDW. When you select the dddw you can see it.

I put the column as a edit field (not dddw) on the form to see what the data was, and it displayed the same wonky character value.

Running the SQL against the database returns the correct value (in this case:  '<100K Population').

Regenerated and rebuilt everything - no difference.

Anyone ever see this before?

Thanks.

Freezing on 2021 Install with .Net Core SDK 3.1.41...
Migration Power Builder
Responses (2)
Colin Cruikshank
Colin Cruikshank Accepted Answer Pending Moderation
  1. Tuesday, 5 October 2021 13:16 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,

Thanks for the reply. Here are the answers to your questions.

1. 2019 R3 Build 2728

2. This is occurring when run out of the IDE, and the compiled 32-bit exe. It is not occurring in the compiled 64-bit exe.

3. Yes.

4. SQL Anywhere 17 version 17.0.4

5. ODBC SQL Anywhere 17 version 17.0.04

Because it is only happening in the 32 bit connection, I will start my investigation there. Thanks in advance for any help!

** EDIT:

Checked the ODBC config for the 32-bit and 64-bit and they are the exact same. Interestingly enough, the weird characters aren't returned when connecting to a different test database (for both 32-bit and 64-bit). I'll check that lead out.

Colin

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 5 October 2021 14:29 PM UTC
Hi Colin ... It could be because the DB with the issues is Unicode encoded and uses data types like NChar and NVarChar. In that case, you need to use a different DB Client ODBC driver. Food for thought.
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 4 October 2021 20:52 PM UTC
  2. PowerBuilder
  3. # 2

Hi Colin;

  Can you tell us ...

  1. PB runtime build number that you are using?
  2. Did you deploy the new XML file with your PB App EXE?
  3. If you edit the DDDW "source" does it state "release 19;"?
  4. What DBMS & version are you using?
  5. What DB Client type is your PB App using (and version)?

Regards ... Chris

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.