Hi John,

"python is the very best replacement for VFP.".

+ 1 here:)

Once you start to evaluate the replacement for VFP strictly as a "computer language" with the same kind of requirements you came down to foxpro (back in times....), this is quite obvious.

Ceteris paribus there is no better replacement to a vfp piece of code than a python one. I had a wonderful experience replacing a foxisapi-based servlet with a modpython one. That was a real joy to code. However life ain't always as simple. The truth is that quite a number of VFPers did not came down the fox way for its exact qualities as a highly expressive interpreter.

They also pondered its specific capabilities in terms of data handling and speedy delivery of decent win32 UI, the corporate support of MS and a few other stuff. Some had experience of compilers à la clipper and liked it. Others would work with any horse and quite a number among us had indeed very little freedom of choice. Either when they jumped our fox bandwagon or moved out of it:(

PS: As far as I am concerned, I have used python on the web and liked it and on my way back to use it via wxpython to translate a significant code base from foxpro to plain vanilla python:) I'd be glad to get pointers on "best practices" to replace cursor-based and local sql DML operations within python. I'be be glad to avoid running via additional database layers whenever possible!