"JodyT" <datagal@msn.com> wrote in message
news:f9d864c3.0408121402.57dab7da@posting.google.com...
> I understand that the XML isn't the dataset... I was just trying to
> use the XML to figure out how things were being handled. Sorry if I
> was unclear.
>
> You're right... I was filtering. The difference wasn't apparent right
> off the bat. I foolishly assumed that if you put a parameter in and
> connected it to a field, it would limit the query.
>
> I removed all of the parameters and rebuilt them (just for the sake of
> starting fresh) and added them to the query. The query runs fine on
> it's own, but the report gives me the System.OutOfMemoryException
> error again. Yes, I have SP1. Because I was also occasionally getting
> System.StackOverflowException, I made sure that my 3 groups are
> grouped and sorted by the same expression.
>
> Now what? I've only been at this for 2 days, but I'm getting close to
> scrapping the whole thing. We're evaluating to see if we can replicate
> our Crystal Enterprise solution in RS and I'm not at all impressed so
> far. I'm seeing many of the same issues I saw on my last contract
> with another rdl based reporting product.
>
> Jody
>
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@hotmail.com> wrote in message
news:<uEHa2jHgEHA.3928@TK2MSFTNGP11.phx.gbl>...
> > Are you filtering or are you applying a parameter to your query. Does
your
> > query look like this:
> > select * from sometable where modifieddate = @mydateparameter or if
against
> > ODBC or OLEDB it would be
> > select * from sometable where modifieddate = ?
> >
> > I guarantee you your query looks like the above, the parameter is being
> > passed to your query. I go against 10 million row tables (returning a
few
> > hundred rows) and it would not function at all if it didn't do this.
> >
> > If you are applying a filter then the filter brings the data over and
then
> > filters it. Big difference (I don't tend to use filters at all).
> >
> > One other point, are you getting this error when trying to get it out in
PDF
> > or do you get it when viewing it in HTML (another way to look at it is
do
> > you get this error when doing a preview in the development environment)
> >
> > One last point, the data is not in XML. The data is in a dataset. The
report
> > is defined in XML, that is all.
> >
> > Bruce L-C
> >
> > "JodyT" <datagal@msn.com> wrote in message
> > news:f9d864c3.0408111349.35b2c2ff@posting.google.com...
> > > I'm fairly new to XML, but it looks to me like my parameters are not
> > > being applied to the Select in the Where clause, but rather sometime
> > > later (that I don't see right off). Could this explain why I can't
> > > even get a report limited to just over 6k records to complete without
> > > an OutOfMemory error?
> > >
> > > The same report, run unlimited, in Cyrstal with over 425k records runs
> > > fine. Both Crystal and RS are running locally.
> > >
> > > Ideas?
> > > Thanks,
> > > Jody