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

Resolved Case Sensitive in PB17

  1. How-to
0
Votes
Undo
  1. Sally D
    Sally D
  2. PowerBuilder
  3. Thursday, 15 November 2018 09:25 AM UTC

Hi all,

 

Just find one issue, when we migrate the PB2012 to PB17, the code should not be case sensitive. But with the new version, there occurs some runtime error if we not keep same case in the code.

For example, we initail the variable 'Test', but when use in the function as 'test', the new version occurs the runtime error. Is this common? We need to keep them the same case, both upper-case or both lower-case.

 

Thanks

 

Transaction's DBHandle() yields DBError
Converting a blob to a string
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 November 2018 14:27 PM UTC
  2. PowerBuilder
  3. # 1

Hi Sally;

  PB2017 is not case sensitive. However, like all PB releases even before it - the use of reserved words could be the issue. To avoid any chance of a reserved word use (even DBMS DML command words - aka In-line SQL), always use a prefix and/or suffix to your names. For example "oe_test", "wn_test", "uo_test", etc.

HTH

Regards ... Chris

Comment
Sally D
  1. Sally D
  2. Monday, 19 November 2018 09:56 AM UTC
Thanks Chris,

I found that runtime error is not caused by the case. If i make the code of that line as comment and then repeat them on a new line. The error is disappear, is that the bug with PB when transmit the info accross window?
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 19 November 2018 17:14 PM UTC
Hi Sally;

I am a little vague on your statement. Can you post a few screen snapshots of the problem so that we can see the issue before & after your code change?

Regards ... Chris
  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.