1. Larry McClain
  2. PowerBuilder
  3. Tuesday, 15 October 2024 19:30 PM UTC

I recently migrated from PB 2019 R3 over to PB 2022 R3.  I rebuilt the .exe (executable) file but I am experiencing a problem.  I connect to my SQL  Anywhere 12 database and run the PB 2022 R3 code in the PB IDE without any problems as it expected.  However, when I run the executable (.exe) file, I am seeing errors like the following:

Select Error: SQLSTATE = 37000
[Sybase][ODBC Driver][SQL Anywhere]Syntax error near ';' on line 1
SQL Syntax = cloud;MTcyNzk3MzkxNg==;UGiZcP+zRsJSbBA3E3rKv7j3vIughJ1rq97dmqH6KdBLMSmZWOVKgMQn0u62Cg/lhB6BCs+5Gz/pwfYlJ7xtx9kaLm1ZTUagZV85S3PWt9S5+9Bfp7eRtAbBigE2VGBslhRpsu3Wp/Mvh9mL8FuYea4nS8oh8k6mxx4zhLmHS3aIun2X4slytgfhatsFmn/cVXj4ajqtL7B504oAoCXh2syk4MjKNAbQl+8+bPrcYsER07WA7wzq9RpDkl/s/M5HkByw504WS7IiRjfggBt2tZFBk51KveF58QOb2f1Yem6+U5mzVOTqdLzwADnv8YRRk/1z6HHup4benn2CskGRyx5Bp+FJXOB5IrbzGeKklMNTjJ4/VmqwOg2CT3fQpI968nSu974OFOgul4vG8SKly491R+n7wC5Ww54jD3fe5b8Zywkb7NEPKNjSESPOEb1nx8Fk/9ADXgXDzQS79yFf6ziQX8agchMZ7KUwUfy3GYgQkx4RiqjzgxMX+ZCIRy7SbVsjFO7cRVpO5YO+cKGmWlsmZmAX/H/X+FJrHlK3kLSbuvmnNrWtQYxxn2VqDXKKT8czFa2p11J3EBzV9NADFv74V4FcmRQGG8pmUp8FLLrsCfNii8stLn+2jB2+tNP0p22uIBRFThSLjjf9kkw8gu6uTM0s8ZjGxztzlhzSFo0PGclJJxSb6v4oUHoiz/w6ZHQqkPx4VEXKGoJimuFR55Hn/T0zap8eU6iBJBRW4FMN3tniy3Co0lMDblfQJEoy

Can anyone tell me if there are issues using SQL Anywhere 12 with PB 2022 R3?  Are they incompatible?  If so, what is solution.  Upgrade SQL Anywhere 12?

Pease advise, thanks...

Larry McClain Accepted Answer Pending Moderation
  1. Wednesday, 16 October 2024 18:18 PM UTC
  2. PowerBuilder
  3. # 1

Yes, so please advise...

Comment
  1. John Fauss
  2. Wednesday, 16 October 2024 19:29 PM UTC
Can you please post the Transaction object properties you are using (mask out any sensitive values)?

Are you able to interact with the SQL Anywhere 12 database using the Database Painter in the IDE? If so, how do the Transaction object properties used by the IDE compare with those used in your application?
  1. Helpful
There are no comments made yet.
Larry McClain Accepted Answer Pending Moderation
  1. Tuesday, 15 October 2024 19:58 PM UTC
  2. PowerBuilder
  3. # 2

Chris,

Yes, that is the case.

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 15 October 2024 20:58 PM UTC
Wow .. that is certainly strange if the environment, DB drivers and DBMS are all the same!

Can you try an SQL trace ... ie: SQLCA.DBMS = "TRACE ODB"

Maybe the SQL trace file will point you to something ( just a guess). HTH
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 15 October 2024 19:40 PM UTC
  2. PowerBuilder
  3. # 3

Hi Larry;

  Are you getting these errors from the App EXE running on the same development machine & using the same DSN?

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.