🚀 go-pugleaf

Hello
I have renamed  all Dbwebdatasources and datasets  unfortunatly same problem
still appearing. What ever page I call  after that page's master record
count is become like a rule  than all other pages master  grids  can scroll
only  as much as first pages mastergrid's recordcound.

Best regard

"Orion" <info@eyhost.net> wrote in message
news:43088f09@newsgroups.borland.com...
> Hello
>
> Well  yes I have same datasetname  as defaultname ( dataset1 ) on
different
> pages  I didnt think it may couse this  I will rename them and try  I will
> see how it goes
>
> thanks
>
> "John Moshakis" <john@moshakis.com> wrote in message
> news:4303e2bf$1@newsgroups.borland.com...
> > Orion wrote:
> >
> > > It looks  like buffer or cache  need be cleared. What ever
> > > code I did try about clearing buffer or cache it resulted with error.
> > > I have fixed this funny thing  by putting  unused hidden dbwebgrid
> > > with unused xml file what contents all master records that  all pages
> > > may use.   So  inventualy  pages could  call their all  master
> > > records because of beginning cache or buffer recordcounts are became
> > > over each page's master recordcounts. Now  my question is that.  Is
> > > there any explanation for this or is this is  dbwebgrid bug  or how
> > > can clear that buffer or what ever else?
> > >
> > > Thanks
> > > Regards
> >
> >
> > Hi Orion,
> >
> > Have you got the same dbwebdatasource or dataset name on different
> > pages? The dbwebcontrols use sessionstate to store their state and it
> > sounds as though they are clashing.
> >
> > If you turn on tracing in your aspx page
> >
> > ie
> >
> > <%@ Page language="c#" Trace="true" Debug="true"
> >
> > and scroll down you can see the session state variables, you need to
> > rename controls so that they are unique.
> >
> > Cheers,
> > John
>
>