>>If you're satisfied that you know VFP, try asking "What would you change about VFP as a development tool?"
>>
>>If they've got no complaints, they haven't used it.
>
>I have no complaints about VFP... :)
>

We all know you're easy, Paul... < g,d & r >

Seriously, there's no right answer to the question - but it gives you a good idea of whether someone has worked with VFP for any period of time.

Let's assume for the moment VFP were 100% free of 'undocumented features". Everyone who's used VFP to do much of anything has things that they'd like to see changed. Just ask Jim Nelson...

When I ask a candidate that question, I'm not looking for a features list, or familiarity with the latest crop of bugs and workarounds; in order to have things you'd like to see changed, you must've tried to use it the way it is now. It's not a question that can be studied for in advance, or that a headhunter can prep a candidate with pat answers based on another candidate's interview summary.

It's a great springboard for discussing the guts of VFP from your own POV. And sometimes you even learn a thing or two that you didn't know about before!

A note to JimN - this'd be your chance to bitch about the state of the documentation at an interview! :-)