🚀 go-pugleaf

James D. Franchello wrote:

> Hello Bob,
> 
> I managed to get it to work but what I had to do was the following:
> 
>       DataSet1.Dispose;
>       DataSet1 := Dataset.Create;
>       lItemCount := daRequests.Fill(Dataset1);
> 
> which seems really inefficient since it implies that on each Pageindex

Then you don't understand how WEB applications work.

This analogy works, albeit, extremely oversimplified:

- Take into mind a Win32 application.
- When you request a Web Page, the application is started.
- When the web page is rendered the application is terminated.

Thus anything created is also destroyed immediately.

> change I go and get all the data again. I guess I just don't
> understand these objects because it seemed to me that once I had used
> the Fill() the data should be available in the dataset so that any

Not in the dataset itself, because the object is destroyed because the
application is terminated.

You would need to store it into the viewstate of the webpage, and in
the repost would need to retreive it from there.

But you don't want that. Pages like these get gargantuan in size real
quick and you don't want to have your visitors waiting 2 minutes on
every repost before they see the new page.

> I am not using the BDP objects but rather the OLEDB objects. Is there
> any particular reason to use one over the other?

What database do you have? Does BDP support your database? If not, use
OLEDB.
BDP == Larger overhead, but better designtime support IF you've got a
higher than PRO SKU. PRO and below (turbo's) and BDP's useless anyways
as you can't bind it to anything because they didn't bother to put in
the components required to do so.