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

Resolved Datawinow

  1. Issue
0
Votes
Undo
  1. Jure Gornjak
    Jure Gornjak
  2. PowerBuilder
  3. Thursday, 25 June 2020 10:02 AM UTC
Dear PB developers,

After a long PB programming career, I encountered an error with only one user (but not in the development environment), the error is shown on end of question .

PB version 8.0.4,
Windows 10 Enterprise,
SQL Server 2008 R2,
IBM ThinkPad laptop (64 bit OS)

I will be grateful for any hint or idea!

Thanks and regards

Jure
 
 
and
 
Encryption-decryption not working
SetRedraw() to reduce flickering
Responses (3)
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 25 June 2020 13:35 PM UTC
  2. PowerBuilder
  3. # 1

it is a datawindow select error.   so, you have a datawindow with bad sql that your database server is rejecting.

what is the datawindow sql?  what is the user doing that causes the error?

 

my guess  is that the user is entering some sort of parameter that is supposed to be a date and they have entered a bad date.

 

 

Comment
There are no comments made yet.
Jure Gornjak
Jure Gornjak Accepted Answer Pending Moderation
  1. Thursday, 25 June 2020 13:00 PM UTC
  2. PowerBuilder
  3. # 2
Dear Kevin,

thanks for your opinion, i think you are right!

1. I have no problems with PB 8.0.4 and Windows 10,

2. I use the latest version of NTWDBLIB.dll to connect to SQL Server 2008 R2 or SQL Server 2016 (I do not use ODBC connection).
Comment
Kevin Ridley
  1. Kevin Ridley
  2. Thursday, 25 June 2020 15:20 PM UTC
Compare the regional settings and let us know if that fixes it,
  1. Helpful
There are no comments made yet.
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Thursday, 25 June 2020 12:01 PM UTC
  2. PowerBuilder
  3. # 3

First I will state the obvious - PB8 was EOL'd and hasn't been supported in ages, and was never supported on Windows 10.  So we recommend you upgrade to PB 2019 so you can be on a supported version.  That being said, to me this sounds like either a regional settings issue on the 1 user's pc and/or maybe a different ODBCXX.ini entry on that pc if you are using ODBC to connect.  Compare that user's datetime settings with a pc that works.

 

Kevin

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.