Logic to serach records from database using SDOs and SDVs

Jasdeep

New Member
I am a beginner to openedge progress. I reviewed the documentation on Openedge progress studio using sample application. I am not able to find anywhere the logic for seraching the records from database.
For Instance in text box the input is given as customer number and on click of button the details of the customer should be displayed in Smart data view.

What will be the logic behind this procedure ?
I am stuck on this from last two days . Please help me in resolving this issue.
 
You don't say anything about the Progress/OpenEdge version you are using. But, since you talk abou SDO and SDV I'll take it that you talk about some version of ADM2. If that's the case then I guess that you are missing the data link from the SDO to the SDV.

Don't get me wrong, but, the ADM2 ( and Dynamics which is based on ADM2 ) are remnants from the last century and there never were many who used it and there certainly not many anymore that use it. My response is just on top off my head - I haven't done anything with ADM2 at least for 10 years now.

If you are planning in developing applications in ADM2 ( or Dynamics ) then you should either bring in a seasoned veteran or attend a proper training. There will be a pretty steep learning curve and most likely you will wind up fighting the frame work instead of using it. The most important thing is to understand the framework.

Heavy Regards, RealHeavyDude.
 
Thanks. But I have to start working on my company's open edge project which will involve these kind of things like serach based on the text entered in the text field.
What other technology in open edge can be used to implement this logic?
 
In the Progress ABL you have four options:
  1. Using one of their frameworks ( ADM2 / Dynamics )
  2. Using a third party framework or templates
  3. Roll your own framework or templates
  4. Code each requirement individually
Naturally you would choose a framework that can save you a lot of time by providing solutions to most requirements and leaving you to individually code the rest. But that also means that you must understand the framework, how it works, where it's strengths and wearknesses are.

Please don't get me wrong: You are not to blame for being in the situation to work with legacy code. But you need proper trainging in order to get things done with reasonable effort and to be able to produce quality code. You must make that very clear to your employer. If they are not willing or able to either provide you with the proper training or pay for it then you won't be able to provide a solution within a reasonable amount of time and quality. Even more so when you have to work with frameworks for which Progress did never provide proper documentation, when the documentation is the code. Full Stop.

I know that won't help to solve your immediate issue - but that is the best advice that I can give you.

Just to be clear: Regardless whether one likes the ADM2 or not, it provides an easy solution for such kind of requirements. Have a look at the smart filter. One of the main concepts of the ADM2 was to provide generic objects ( SDO, SDV, SDB ... SDx - you name it ) from which you can inherit and create your custom instances mostly be setting their properties and putting custom code in overrides of standard behavior. You then can place them on a smart container ( smart window for example ) and link them via smart links ( which is basically subscribing the objects to events published by their link sources ). Then you are done. This allows to create a simple maintenance screen with search capabilities without much effort - if you are an expert maybe in a few minutes. But being an expert you need to know a lot about the framework's internals which are basically hidden in the code of the class super procedures. As I already mentioned Progress failed miserably to provide proper documentation and sample for that framework but that is not an argument against the framework itself - it is an argument for blaming Progress not being able to provide proper documentation.

Heavy Regards, RealHeavyDude.
 
Back
Top