>From my experience, one of the most important (while apparently innocent :)) question is:
>
>What (if any) source/version control software are you using?
>
>If they don't use any... keep looking! :)
>
>Another important question is if they use third party components. If yes, which ones. If no, why? The truth is that nobody can develop everything, so, if they still do it in this way, they must have a very solid reason. Otherwise, you may find yourself in a company that dies developing the wheel again and again.
>
>And you should always ask what are the current versions in use for VFP, Windows, etc.
>
>Vlad

One more point that is non-obvious, but which bit me big-time on a previous job -- even though asking about standards and practices was included earlier:

I want to see source code. One job interview at a major national grocery chain headquarters included a pseudo-competency test, which would have led me to believe they were really looking for a high-level FoxPro person to supplment their own high-level staff. When I got in the door, their coding style (which was 'standardized' internally) was so bad, obtuse, dBase-2/3 level, highly macro driven, poorly named fields and files, **intentionally** disconnected CDXs (different name CDX from base DBF!) that I was there over 3 months before there was any hope of writing meaningful code into their system. If only I had looked at their source code first, I would have walked away -- no, RUN away, as fast as I could...

Also, I was there as a contractor at the time, and although I asked about what hardware was being used for development, and got a satisfactory answer -- that was for the full-time employees, and the contractors got the worst crap hardware to use themselves. At that time, it was high-end 486's with pretty good RAM for the FTE's but the contractors got 486-sx25's with 4 MB of RAM. On a Token-Ring network! Took 95 seconds to start MS-Mail, 115 secs to exit MS-Mail... Forget about load time for FP and the apps themselves... So -- be sure to ask what equipment YOU will be using, and how often does it get upgraded. Vlad's suggestion about OS versions is good, but without corresponding info on the H/W, it may not matter...

Rob