2-SDO Configuration

rkh

New Member
Just wanted to find out if anyone had similar or alternate methods...

In order to minimize netwrok traffic between standard 4GL client and AppServer when working with larger records, I'm using 2 SDOs for one table. One is query-only passing key fields for UI selection from a list, and the other passes the entire record (via serverSendRows w/a single RowIdent) for updating when a record is selected. Due to the constraints of the RowObject table, this seems like a resonable approach to maximizing perfomance. Anyone agree or differ?

------------------


<FONT COLOR="#000000" SIZE="1" FACE="Arial, Verdana">[This message has been edited by rkh on 09 March 2000 @ ]</font>
 

Chris Kelleher

Administrator
Staff member
I am using the same method here for our applications. We have a few tables that can be quite large, our customer/client table is a good example. I have a few SDOs with a small sub-set of fields, one for combo-boxes, one for a summary display in other windows, etc. This is a good way to reduce network traffic.

HTH.

-Chris

------------------
Chris Schreiber
ProgressTalk.com Manager
chris@fast4gl.com
 

rkh

New Member
Cool. At least I know we're not alone. It's nice to be validated. Thanks.

------------------
 
Top