>>Could have to do with the way VFP is handling the system messages. If I had to >hazard a guess, that's probably the problem. Unfortunately, this is outside >the realm of my knowledge. Perhaps someone else might have an idea. You might >want to post the original VB code, however. There might be something there >that might give us more of a clue
>
>George
>
>The link for the VB source code is here
>
>If you look at the link you'll see I've stripped it to the bones and just got the declaration and the parameters from it. At the start it seemed like a 5 minute job to do but.....
>
>Anyways, what the heck, it's Friday afternoon - playtime!
>
Paul,

Well, I finally got around to looking at this, and I'm afraid that it seems to confirm my guess as stated above.

I was able to implement the form as the article specified without problem in VB. In VFP, it was another story.

In VFP 6.0 SP5 I created a form, and like you, confirmed that the window with the Auto-Suggest Dropdown class did exist. I even tried grabbing its window handle (which I did) and issuing a call to ShowWindow() with SW_RESTORE. The best I could get was to make the window "flash" in the upper left hand corner of the VFP screen with each key press.

I then copied the form into the VFP 7.0 Beta 1 directory and tried again. A bit more luck, but still not what you'd want. The Auto-Suggest Dropdown again appeared in the upper left corner and stayed. Unfortunately there was no information in it that could be accessed. Further, the window persisted until after I closed VFP.

I think that my reaction that this may be tied to VFP's message handling may be correct.

Sorry,

George

Ubi caritas et amor, deus ibi est