A method that I used for a user to find out his or her employee id was by having a 'search for employee id' link on a page next to a text field where the user is to enter his or her employee id since most employees don't know it.
This caused a new window to display, allowing the user to enter in his or her name. They enter their name, hit submit, and in the same new window, the results were displayed. When the user selects one of these, the javascript populates the main browser window (the one that launched the search page) and the new window closes itself. "Slava_L" <[EMAIL PROTECTED]> writes: > that's quite nice way.. but then i will need to truncate search > results if they are "too big" to be send on client, wont i ? In the above app, if the search resulted in only one record, then that record was used to populate the main browser window, otherwise it displayed all the results (which probably wasn't very wise in retrospect). Perhaps if the results are, say, over 25 records, then you could ask them to be more specific or perhaps make pages for them to select from - such as when you use a search engine on the web and receive a great deal of results - 25 each page or whatnot (and perhaps with a text field to re-do their search since at that point they'd realize that their search wasn't specific enough). An extension to the above method is by using javascript to initiate the first query on the pop-up window, too. If there is only one result then javascript populates the calling window (such as when a user is pretty sure that the street name is correct but wants the system to do a quick check; perhaps feedback could be provided in the status bar). hth, Elizabeth > ----- Original Message ----- > From: "Dan Cancro" <[EMAIL PROTECTED]> > To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> > Sent: Friday, June 21, 2002 10:01 AM > Subject: RE: how to solve a problem of fetchin' HUGE collection into form > > > > It sounds like you need to replace your drop down box with a link to a > > search screen. On the search screen, the user types in a few letters and > > the system displays just the streets that start with those letters. Then > > the user picks one and goes back to the form. > > > > > > > -----Original Message----- > > > From: Slava_L [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, June 20, 2002 5:49 PM > > > To: Struts Users Mailing List > > > Subject: how to solve a problem of fetchin' HUGE collection into form > > > > > > > > > I have a form with several fields. > > > And one of them is SELECT field - 4xmpl streets names. > > > All streets names are stored in database, amount 100-300 > > > thousands records > > > And the problem is that when this field renders on the page, > > > app is freezing for a long time. > > > how am i suppose to solve kinda problem ? > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
