Creating SQL-Like Views from Progress for report writing

Chuck Stoops

New Member
I am probably not as technical as most of you, but in our small business I am the Tech-Guy. We are currently converting over to SX, which means we're converting from a SQL to Progress database. WE have extensively used SQL Views to facilitate creating Crystal Reports for various reports. What we'd like to do is create a "View" from the Progress database to emulate the same data structure as in our current Crystal Reports. The idea is to keep the same logic in Crystal and massage the data coming in. I don't think we have the budget Bravepoint's software. What would be the best way to do this? Thanks!
 
Re: my original question. I wanted to point out what software we have available: Openedge 10.2B, SQL Server Management Studio 10.50.1600.1 and Visual Studio 2008.
 
For SQL access, the OpenEdge database supports creating views.
Thanks!
Would the view would be created in Openedge and read by SQL? Or, would the data be loaded into SQL and the view created there?
My consultant is telling me that the Progress tables can only be loaded in SQL Server Management Studio as a linked database and as a linked database in SQL Server Management Studio is is not allowing us to create views.
 
I believe that SQL Views are created from the SQL side ... they aren't visible in ABL. If nothing else, use the provided SQL Explorer tool ... not fancy, but it works when nothing else will.

Note also that if you use triggers, SQL can't see the ABL triggers and vice versa.
 
I believe that SQL Views are created from the SQL side ... they aren't visible in ABL. If nothing else, use the provided SQL Explorer tool ... not fancy, but it works when nothing else will.

Note also that if you use triggers, SQL can't see the ABL triggers and vice versa.
When you say "from the SQL side", do you mean via an ODBC connection?
 
You're new to Progress.

Rule #1 -- Progress is not SQL. Progress does support SQL-92 access via ODBC/JDBC but SQL is not its native tongue. Applications, such as SX, speak to the database using the 4GL (sometimes referred to as "ABL" but that's just marketing weasels speaking with a forked tongue...).

Rule #2 -- The more you try to think of Progress as a SQL database the more frustrated you will be. See rule #1.
 
If you are going to use SQL to access the database, I would recommend trying to stay current on the Service Packs, they contain many bug fixes related to SQL. In one of our systems, just going from 10.2B05 to 10.2B07 made a difference.
 
Back
Top