Subject Re: [IBO] More than one Lookup combo to one dataset
Author Marc Leclerc

My initial problem for asking this question is that I have a table with a
list of names and a table that uses those names for fields such as
ReceivedBy, ApprovedBy, ForwardedTo, DecisionBy,... What I have to do now is
set many queries (one for each field) and I though there could be a better
way such a cloning one dataset in order to reduce the number of queries that
need to be executed. The table, as mentionned earlier, are fairly small so
the impact is not so bad for this case, but I was wondering what I could do
if the table were big.


----- Original Message -----
From: "Jason Wharton" <jwharton@...>
To: <>
Sent: Wednesday, March 14, 2001 2:00 PM
Subject: Re: [IBO] More than one Lookup combo to one dataset

> Michael,
> There is no advantage of this over simply using a separate dataset. One
> thing that you can do is fetch all the rows and then call
> FreeServerResources. What this does is release the statement handle that
> dataset holds. This makes it purely a client container for rows in memory
> from the server.
> So, consider this done...
> Jason Wharton
> CPS - Mesa AZ
> ----- Original Message -----
> From: "Michael L. Horne" <guardian@...>
> To: <>
> Sent: Wednesday, March 14, 2001 9:42 AM
> Subject: RE: [IBO] More than one Lookup combo to one dataset
> > Hello
> >
> > What would be great for this is a new control that connects to
> > the dataset, loads the data, disconnects, and remembers its
> > data. Has methods to refresh, clear. And would work like
> > the LookupCombo. This would solve the problems of multiple
> > Datasets and would also be very useful for those small standard
> > datasets that don't change very often, like Terms, or Warehouse
> > .... You get the ideal. - - - - Maybe one of the genius here
> > could write it for us?
> >
> > Michael L. Horne
> Your use of Yahoo! Groups is subject to