1. Douglas Lee
  2. PowerBuilder
  3. Wednesday, 28 August 2019 21:19 PM UTC

I'm trying to generate C# web service for a progress database and keep getting the error....

[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Syntax error in SQL statement at or about ") = 'autoincrement' then 1 else 0 end AS" (10713)

I've done some research and it seems the problem is that Progress doesn't allow semicolons as terminators.

https://knowledgebase.progress.com/articles/Article/000032174

Is there a work around i can do to get this to work correctly?

Douglas Lee Accepted Answer Pending Moderation
  1. Thursday, 29 August 2019 13:07 PM UTC
  2. PowerBuilder
  3. # 1

Thank you for your response, will keep my eyes pealed for Progress being added to the list.

Comment
  1. Miguel Leeuwe
  2. Saturday, 31 August 2019 10:24 AM UTC
With no disrespect to anyone, but I think you'll be better of trying to find an alternative way to get your data. I don't think that Progress ODBC is very high on Appeon's list of priorities. Hopefully I'm wrong.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 28 August 2019 22:03 PM UTC
  2. PowerBuilder
  3. # 2

The only database officially supported using ODBC interface is SQL Anywhere, and the other databases have native .NET Core drivers:

  • SQL Server
  • Oracle
  • PostgreSQL

I think your problem is that you are using a database that is not supported.

Please refer to "Database Connections" section of the product documentation: https://www.appeon.com/support/documents/appeon_online_help/powerbuilder/features_list/

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.