How to create connection to Progress OpenEdge data source?

4 posts, 0 answers
  1. Rom
    Rom avatar
    3 posts
    Member since:
    Jun 2015

    Posted 16 Jul 2015 Link to this post

    What are the recommended 'best practices' steps to connect the Telerik Standalone Report Designer to a Progress OpenEdge database and to persist this data connection for subsequent reuse with the standalone Report Designer tool?   Thank you!  
  2. Stef
    Admin
    Stef avatar
    3053 posts

    Posted 16 Jul 2015 Link to this post

    Hello Rom,

    Telerik Reporting provides data source components that can be used to connect data to reports:
    1. You can use the SqlDataSource component and the installed on the machine .NET data providers to get data. The Standalone Designer tool has AnyCPU and x86 versions that can be used with respect to the available .NET data providers on the machine.
      Only the Query Builder will not be active in case you use a database  not officially supported by Telerik Data Access as in the case.
    2. Data can be consumed via data service in code and connected via an ObjectDataSource component. Please consider the example in Connecting Telerik Reporting to OData feeds.
      The ObjectDataSource can be used also if you have the data in XML or JSON format, where the content first must be loaded in a .NET object.
      In order to use an external assembly with the data access logic in the Standalone Designer, the assembly must be loaded by the tool before starting it - Extending Report Designer.

    Let us know if you have any further questions.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. DevCraft banner
  4. Akshay Deep
    Akshay Deep avatar
    2 posts
    Member since:
    Aug 2015

    Posted 26 Oct 2015 in reply to Stef Link to this post

    Error while using "Query Builder"

    I have connected to OpenEdge database using SqlDataSource Component.
    Seeing an error on using the QueryBuilder, steps followed to make connection are:
    1) Created a dsn for OpenEdge databse.
    2) Selected a Table Wizard for Data Presentation Templates.
    3) Clicked on 'Add New Data Source...', selected SQL Data Source.
    4) Build a new data connection, for the datasource created.
    5) In the window- "Configure data source command", click on "Query Builder", 
    error shown is- 
    "ERROR [HY000][DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Syntax error in SQL statement at or about "@@version"(10713)"

    What can be the issue causing this error? Has anyone else reported this issue earlier? 

     

    Thanks,

    Akshay

  5. Stef
    Admin
    Stef avatar
    3053 posts

    Posted 26 Oct 2015 Link to this post

    Hello Akshay,

    If you are using the Query Designer built in the Standalone Designer tool, it works based on Telerik Data Access and the databases listed here.

    If you are referring to the Query Builder in Visual Studio Report Designer, it is actually part of VS, and issues can occur if the used .NET data provider is built with different platform target than the application (x86, anyCPU).


    In both cases:
    1. The SQL statement and parameters can be configured manually;
    2. You can build data access layer, used in reports via Object/Entity/OpenAccess DataSource component. Using these data source components allows you to consume also data delivered by a data service e.g. Connecting Telerik Reporting to OData feeds.


    If you need further help, feel free to open a support ticket and send us more details which report designer is tested, and the exact steps how to reproduce the problem.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top