ADM2 and the Appserver

P

paul_pichette

New Member
Couldn't find much help in the Progress Knowledgebases, so I thought I would give you all a try...

How complex is it to make a standard ADM2 (using core objects) to work with the Appserver?

Any suggestions of nightime reading material I should have?

9.1C
 
The answer is fairly.

You should specify the AppServer for the SDO using the object properties. The sdo_cl.r gets distributed on the client and the sdo.r gets distributed to the server.

There are functions within the SDO that allow you to check whether you are running on client or server and the appropriate handles, and along with proper use of the db-required-start and db-required-end pre-processors, you can call a procedure from client side and have it run itself on the server.

An alternative, and we have found quicker running, method is to use SmartWindows, SmartFrames, SmartEditors... but to handle the database calls through standard appserver calls.

I don't know of any specific texts that deal with this subject.
 
I would expect ADM2 & Appserver integration to behave more than just 'fairly'...

Any particular pitfalls you remember that caused you to shift gears and develop your own function calls to the Appserver?
And do you then not use the SDV/SDB - SDO (rowobject) mechanism?

Paul.
 
It's not that they behave fairly. It's the complexity that's fairly.

For our more involved programs we tried to avoid using the SDO's for performance reasons.

Consider if you had a table with 6 foreign key fields. You might consider representing each of these fields on the smart data viewer by smart combos or lookups so the user could see the valid options. But each smart lookup requires its own SDO.

It just worked out faster to load standard combos using appserver calls and populate/read them as necessary.

Also one program's endTransactionValidate can be very different (or completely at odds) with another program's for the same SDO. Do you then have 2 SDO's for the same table?

We still use the SDO/SDV/SDB mechanisms but not exclusively.
 
Ok, thanks for sharing your experience.

Currently the small application doesn't have 2 SDO's for the same table, what problem would that cause? (I guess this question is probably because I haven't used the EndTransactionValidate Override...).



Paul.
 
You must log in or register to reply here.
Back
Top