Two filter/search screens?

[Bob Hansen]

Hi there,

I'm trying to create a filter screen after a filter screen. In the First screen I want to filter the database on geographically location(from the database records!) and on the second screen I want to filter this recordset for town(also from the database!) or something else.
I don't want to show any records on the filter screens.

is this possible with EP?
(version 2.2003)

Any help would be appreciated!

Kind regards,

Bob Hansen

[Mark]

Hi Bob,

I cannot think of any way to do it. I assume you want to do it this way
(as opposed to putting both the "location" and "town" on the same screen)
because you only want towns on the filter drop list to be the towns from
that chosen region?? I think you would need to do it in two passes, going
back throught the grid after the first pass, then clicking [Filter] a
second time. Even then, you'd have to alter your SQL statement to do a
WHERE Location = "xxx" after the first filter or else you'd STILL get all
the towns on the second filter screen.

Another possibility would be to write your own "pre-filter" screen as in
example D5a, then use dbStartup="Filter" to go right into a filter screen.
This would assume that you could know the list of all "locations", assuming
you wanted them to appear on a drop list. If the user could just TYPE in a
location, you'd be all set.

I suppose you could also detect that an [Apply Filter] was just performed
then redirect the asp program to another asp program where
dbStartup="filter" and define the dbSQL to include a WHERE clause using the
answer from the first filter.

Does this make sense?

Mark.

[Bob Hansen]

The Last option seems the best, but how do I detect apply Filter?
request([apply filter]) <> &#34;&#34; maybe????

Thanks,

Bob Hansen

------------
Mark at 8/23/99 9:39:12 AM

Hi Bob,

I cannot think of any way to do it. I assume you want to do it this way
(as opposed to putting both the &#34;location&#34; and &#34;town&#34; on the same screen)
because you only want towns on the filter drop list to be the towns from
that chosen region?? I think you would need to do it in two passes, going
back throught the grid after the first pass, then clicking [Filter] a
second time. Even then, you&#39;d have to alter your SQL statement to do a
WHERE Location = &#34;xxx&#34; after the first filter or else you&#39;d STILL get all
the towns on the second filter screen.

Another possibility would be to write your own &#34;pre-filter&#34; screen as in
example D5a, then use dbStartup=&#34;Filter&#34; to go right into a filter screen.
This would assume that you could know the list of all &#34;locations&#34;, assuming
you wanted them to appear on a drop list. If the user could just TYPE in a
location, you&#39;d be all set.

I suppose you could also detect that an [Apply Filter] was just performed
then redirect the asp program to another asp program where
dbStartup=&#34;filter&#34; and define the dbSQL to include a WHERE clause using the
answer from the first filter.

Does this make sense?

Mark.

[John]

Hi Bob,

Check if Request(&#34;aspDBClick_unitno&#34=&#34;applyfilter&#34;

If so, it was just clicked. You might also want to check X.dbRecordCount>0 to see if any records were found before heading off to the &#34;next&#34; screen.

Hope this helps!
John


------------
Bob Hansen at 8/23/99 9:52:19 AM

The Last option seems the best, but how do I detect apply Filter?
request([apply filter]) <> &#34;&#34; maybe????

Thanks,

Bob Hansen

------------
Mark at 8/23/99 9:39:12 AM

Hi Bob,

I cannot think of any way to do it. I assume you want to do it this way
(as opposed to putting both the &#34;location&#34; and &#34;town&#34; on the same screen)
because you only want towns on the filter drop list to be the towns from
that chosen region?? I think you would need to do it in two passes, going
back throught the grid after the first pass, then clicking [Filter] a
second time. Even then, you&#39;d have to alter your SQL statement to do a
WHERE Location = &#34;xxx&#34; after the first filter or else you&#39;d STILL get all
the towns on the second filter screen.

Another possibility would be to write your own &#34;pre-filter&#34; screen as in
example D5a, then use dbStartup=&#34;Filter&#34; to go right into a filter screen.
This would assume that you could know the list of all &#34;locations&#34;, assuming
you wanted them to appear on a drop list. If the user could just TYPE in a
location, you&#39;d be all set.

I suppose you could also detect that an [Apply Filter] was just performed
then redirect the asp program to another asp program where
dbStartup=&#34;filter&#34; and define the dbSQL to include a WHERE clause using the
answer from the first filter.

Does this make sense?

Mark.