I didn't think your idea was half baked...it was real close to mine... *g*

I had forgotten the NODEFAULT and was wondering why it was still behaving the way it did by default (he says shaking his head)

I can live with the behavior as it is...I just hoped for more...and more and...

Now if I could just learn "Design"...preferably in my sleep.

BTW - I'm serious about learning design. I recognize that my OOP skills are still weak but my OOD skills are currently infantile. I've been at VFP for about 1 year, and I'm just wrapping up my first full project. (my users like it a lot...and have been instrumental in its development) I've read "The Hacker's Guide", "The Pro's Talk", and "What Every Programmer Should Know About Object Oriented Design", but that's all. In my environment it's not likely that we'll hire a mentor. I may be able to do one event/training per year. Resource materials can be purchased, as can be tools. The UT has been my single biggest boon. If you have any suggestions I'd love to hear them.

Rick
------------
>Rick,
>
>Well, my reply was a rather half-baked idea wasn't it.. *g*
>
>I don't see anyway around this space issue, you may have to code the incremental search on your own. You can alter ListIndex inside KeyPress to simulate it.
>
>>I just tried what you suggested...here's my code in the cbo keypress:
>>
>>LPARAMETERS nKeyCode, nShiftAltCtrl
>>* capture the spacebar and treat it as a space
>>* and not as a selection indicator
>>IF nShiftAltCtrl = 0 AND nKeyCode = 32
>> * Spacebar was hit
>> NODEFAULT
>> This.value = This.Value + " "
>> This.Refresh()
>>ELSE
>>ENDIF
>>
>>It no longer acts as the selector when I hit the space bar (yea!!) but it does stop the incremental searching. Is there a way to keep the search going?