Conner -
One word of warning. Relying solely on the length of the BAQReportParameter.Filter01 field might not be suffcient. The text in that field my contain other variable length data (such as userid) so look at the full text of the field before deciding.
Calvin
One word of warning. Relying solely on the length of the BAQReportParameter.Filter01 field might not be suffcient. The text in that field my contain other variable length data (such as userid) so look at the full text of the field before deciding.
Calvin
--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Thanks, I think this will work like I was envisioning.
>
> --- In vantage@yahoogroups.com, "c.krusen1" <ckrusen1@> wrote:
> >
> > You can check if filters have been used by using the BAQReportParameter.Filter01. It's a string that will actually have XML code in it.
> >
> > You could simply check the length of the string to see if it's shorter than however long it is with nothing selected for the filter. Then display message and suppress all other sections.
> >
> > This won't make the BAQ run faster, but would save you reams of paper if run "incorrectly".
> >
> > Calvin
> >
> >
> > --- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@> wrote:
> > >
> > > Hi,
> > >
> > > Just wondering how others make a criteria required on BAQ reports.
> > > -- Especially when there are multiple options & filters available.
> > >
> > > I see some BAQ reports that are huge when a user forgets to enter an option/filter.
> > >
> > > Thanks ahead of time...
> > >
> >
>