Hi Rick,

I'm changing subject.

In the past i've read a lot of convincing arguments in favor of VFP both on you site and in your great "vfp and Interner" book. In view of the kind of applications I currently develop, I want to stay on the "interpreter side" of IT. A la fox or à la python.

I'm still considering python despite it clearly lacks productivity backup. Have you tested the IronPython with a VFP developper mind? or have had feedback by VFP developpers upon it?

The tool has moved extremely fast into 1.x. Which possibly mean something in terms of maturity and intellectual clarity. I'd be glad to consider Ironpython instead of VB net.

The bad luck is that it looks likke you need to be a Net guru for a start. Which currently defeats the purpose of a python highly dynamic DotNet-based interpreter.

I'll be vfp-ing till I make a switch for a new toolset. Still not really finding an acceptable alternative to VFP.

Francis