yes, the way I read it, it wasn't quite clear to me.

cheers
Mark

HB> It seems you missed the point I made in the first response. Your m/d
HB> approach is the right one when you have a big dataset. I did point out
HB> that the "whole row" approach is handy for small datasets...

HB> /ends


Thursday, November 13, 2003, 3:32:44 PM, you wrote:

HB> At 03:27 PM 13/11/2003 +1000, you wrote:

>>Hi Helen,
>>
>>HB> Correct. Any fields from the dataset that you don't want displayed in the
>>HB> ib_grid, just set their Visible field attribute to False. You can
>>also set
>>HB> other Grid things for the column, such as the caption, width,
>>alignment and
>>HB> so on.
>>
>>ah, but that will cause ALL of the data to be fetched from the
>>database uppon moving from one record to another.
>>
>>The concept I'm after is to minimize this fetching of records, so that
>>whilst browsing a grid, only 3-4 fields are displayed, then when the
>>user presses, say "Edit", they get a second screen (or whatever) that
>>contains all of the fields (not just the 3-4).

HB> It seems you missed the point I made in the first response. Your m/d
HB> approach is the right one when you have a big dataset. I did point out
HB> that the "whole row" approach is handy for small datasets...

HB> /ends

HB> Helen




HB> ___________________________________________________________________________
HB> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
HB> without the need for BDE, ODBC or any other layer.
HB> ___________________________________________________________________________
HB> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
HB> keyword-searchable FAQ, community code contributions and more !

HB> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/