🚀 go-pugleaf

Hello Marco,

Thanks for your kind response - I do understand it a little better now (you
were absolutely right about my understanding of Web apps ... sadly ...
sigh...).

I guess the thing I just could not wrap my mind around was the fact that if
a request involved, oh, let's say hundreds of records, and they were paged
10 at a time then each time I wanted to get the next 10 (or prior for that
matter) I would have to go get those hundreds of records again. Once you
pointed out the utterly obvious about the dataset it makes a lot more sense!

This application is currently using an Access database but may at some point
be converted to SQL server. It will only be used in a single manufacturing
facility on the server on the LAN.

Actually, I am using the Enterprise version.

I did manage to get things working with OLEDB. Now I am trying to deal with
how to deploy it (what files need to go where and what access rights have to
be assigned).

Thanks again,
James


"Marco Caspers" <HexorHaxor@vaxor.com> wrote in message
news:45a33994@newsgroups.borland.com...
> 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.