>>I will agree with you wholeheartedly about the switch to VFP. I had the advantage of having dabbled in VB a little. My biggest problem to date has been having to work in both FPW and VFP and keeping everything in my head straight.
>>
>>Your point about your experience (mine is quite similar) does bring up an overlooked fact. Those of us who came into VFP knowing the structured programming paradigm had an advantage over those who did not. This is because they many of the same principles (in fact, I'll argue 'til I'm blue in the face that OOP grew out of structured programming) and goals. This knowledge that we brought with definitely eased the transition considerably.
>
>George,
>I see you have the same problems as me re FPW/VFP simultaneously. I have just decided to jump in on this mammoth thread (how did it start?). How do you update a pop-up list in a FPW screen based on the contents of a textbox on the same screen? (I had this the other day - simple in VFP but darned if I could find a way in FPW). Your other point above re structured programming - I learned C about 10 years ago and forced myself to write EVERYTHING in a modular fashion. Since then I copied this across to dbase/vpinfo/foxpro/fpw and now I have started on VFP, it's a doddle to convert! BTW remember VPInfo (the days when dBase could not handle low level file handling). Regards,

Nigel,

The only time I used popups were with the code that GENMENU generated or for mover lists. Otherwise, for dropdowns, I mostly used arrays. Applying that to your situation, I'd just call a search routine in the edit field's valid routine, to locate the item in the array and set the control value accordingly. Once found, then:

SHOW GET m.var

doodle?!? Does:

doodle = easy

or

doodle = hard ? :-)

I never worked in dBASE, I started with FoxBASE+ 2.10, and really never had any need for the low level functions until, fortunately, they were available (FP 2.0, I think).

George