Storing results of Select Statement

[maploosh]

I have a progress program where I query the database using a couple of select statements. My question is how do I store the data that is returned from a Select statement in progress so I can use it later on in the program?
Thanks
Matt

 

[jongpau]

I have a progress program where I query the database using a couple of select statements. My question is how do I store the data that is returned from a Select statement in progress so I can use it later on in the program?
Thanks
Matt

Hi Matt,

A sample of your code would be helpful. Also, where does this code run? Is it truely a Progress procedure? In that case, why not just transform the SQL to native 4GL/ABL? Also you will have to take into account that embedded SQL will no longer be supported in future Progress versions (or so I have been told by someone at Progress), so if you stick with this type of solution you may get some problems in the future.

 

[maploosh]

I am just curious to see if there was a way that I could store the results of an embbed SQL select statement into a table in progress. Usually I do this by using foreach statements or other native 4GL code. As for embedded SQL not being supported anymore, I have not heard or read anything about that but I appreciate you telling me this because I will take that into account.

Thanks
Matt

 

[joey.jeremiah]

i think, the embedded sql89 which by the way has nothing to do with sql92 engine and it's features and capabilities has been deprecated for quite a while.

though, you don't have to worry about any programs that stop working or backwards compatibility issues, there are no plans to remove deprecated features. at some point the compiler will start issuing warning messages for deprecated and obsolete features.

you can always check what features have been deprecated in the new and revised features doc.


posted by Salvador Vinals @psdn.com

http://www.psdn.com/library/thread.jspa?messageID=4171&#4171

We are not planning to remove the deprecated features and functionality from the product. There's a document that includes information about this, but there is a typo and we are in the process of correcting it.

We are planning to wrap the deprecated features with a compiler (and/or a startup) parameter to provide a warning to the users when using these features. However, again, there is no plan to remove the functionality from the product.

The objective of the deprecation is to set the expectation that those features are considered obsolete and therefore customers should start planning accordingly, having plenty of time (multiple releases, 10.0, 10.1, 10.2, etc.) to proceed.

Finally, the deprecation is exclusive to OpenEdge 10, no change is being done to V9, that would compromise existing deployments.