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

Resolved data window error

  1. How-to
0
Votes
Undo
  1. Andrew Davis
    Andrew Davis
  2. PowerBuilder
  3. Wednesday, 12 August 2020 13:14 PM UTC

Hi, hopefully someone can help

I am getting an error in my application which is 32 bit pb2019 when i run it on windows 2016 RDS

Error = 

datawindow error

Select Error: Decimal conversion error. Powerbuilder supports only 18 digits.

Also on some datawindows I get chinese characters instead of ABCD etc

I do not get this error on another application, accessing the same database, running on the same machine, the difference being as far as i can see is this application was migrated from pb5 to pb2019 the other was written from scratch - i don't know if this is relevant.

However the application runs perfectly on a windows 7 machine

 

Any ideas ?

 

thanks in advance

Andrew 

  1. Database Driver
  2. DataWindow
error calling external object function RUN
PB 2017 R2 Crashed on Second Execution of Stored P...
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 August 2020 15:04 PM UTC
  2. PowerBuilder
  3. # 1

Hi Andrew;

  Newer PB versions support up to 28 digits.

  Sounds like old DataWindow source that was not migrated. Try editing the DW "source" and see if the 1st line says "release=19". If not (especially for the decimal based column DWs), then change the release number & save the source. That should then bring the DW up to 28 digit support.

HTH

Regards... Chris

Comment
There are no comments made yet.
Andrew Davis
Andrew Davis Accepted Answer Pending Moderation
  1. Monday, 17 August 2020 10:31 AM UTC
  2. PowerBuilder
  3. # 2

Chris

Some of the datawindows were not the release=19, but that has not solved the problem.

I am not using more than 3 decimal places anywhere in the application 

Also - any ideas on why the 'chinese' characters show on alpha fields ?

 

FYI - I modified a working application - to just open the first window that was giving me the problem and it worked no error or odd characters, by the time i had all my code copied into the application i have the same problem again. 

thanks

Andrew

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 18 August 2020 17:33 PM UTC
Hi Andrew;

Yes - sort of a StayCation but here in Canada all the waterways are open, so no restrictions on boating and fishing - which suits me. ;-)

Since this is SA, you must be using the ODBC client. Do the App(s) that work and the non-working one use the same DSN? If not, what might be the difference(s) between the two? Maybe that could be your issue.

Regards ... Chris

  1. Helpful
Andrew Davis
  1. Andrew Davis
  2. Tuesday, 18 August 2020 17:43 PM UTC
they use the same system dsn - and connect to the same database.



Its weird - i created a new pbw, application and project, started with the code from one of the other applications, it all worked, ( opened the 'test window' ) i then added in the pbls and then the copied the code for the application open and close and it stopped working. But i have no unusual code, nothing complex that i can see. and it fails to open the same test window.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 18 August 2020 18:00 PM UTC
Hmmm ... I wonder if you have some corrupt Object Classes in your PBL's that were not migrated properly. Have you tried optimizing all your PBL's, Restarting the IDE and then performing a Full Build from the Target Object?
  1. Helpful
There are no comments made yet.
Andrew Davis
Andrew Davis Accepted Answer Pending Moderation
  1. Monday, 17 August 2020 10:36 AM UTC
  2. PowerBuilder
  3. # 3

please see attachements

Attachments (2)
MWSnap173 20200817-113327.jpg MWSnap173 20200817-113327.jpg
MWSnap172 20200817-113237.jpg MWSnap172 20200817-113237.jpg
Comment
Andrew Davis
  1. Andrew Davis
  2. Monday, 17 August 2020 10:39 AM UTC
could it be something to do with the fact that powerbuilder change from unicode or something and the app came from pb5
  1. Helpful
John Fauss
  1. John Fauss
  2. Monday, 17 August 2020 14:10 PM UTC
Is your application using a third-party DLL, custom control or OCX, or any Windows API functions? What font(s) are you using? Typically, when a pre-version PB 10 app is migrated to version 10 or higher and you start seeing international characters like this, ANSI (single-byte) character data is being supplied to the app and is now being interpreted by the app as Unicode (2 bytes/character) data.
  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.