Victor,

Pretty cool idea sir. I would like that idea in my arsenal as well. =)

So, I guess showing the first X rows is a bad idea for CS Data Entry Forms. =(

Thanks!

Dennis


Demographics.accountnum,?lnChars) = ( ?lcaccountnum ) AND Chartlist.StatusCode = 'New' ORDER BY Demographics.ACCOUNTNUM

The important thing here is this part:
WHERE LEFT(Demographics.accountnum,?lnChars) = ( ?lcaccountnum )

...so you pass two parameters - one for the number of characters they've typed in, and one for the characters themselves. I usually let the users onfig how many characters they must type in before the searching/narrowing starts to happen - obviously if you have a lot of data you want more than just 1 or 2 chars entered before you try to search so the result sets are not so huge.

Of course then you have to design the front-end to handle all this, which also can turn out to be a real pain. You need a textbox that knows when you're searching vs editing - and when you searching you need to have a grid auto-popup below the textbox - and then you have to deal with all the arrow keys a user can hit on the keyboard and what happens when they hit TAB ..etc etc etc.

It's a little complicated to get it going the first time you try to do this - but like I said - the users really like it.