Hi John,

I have been a relatively vfp-to-python convert. Great experience but that was by the end of the previous millennium though:).
But only a mean to move from foxisapi to python servlet generations. Never played with UI from VFP. Looks like a hassle.

I am now tiptoeing on wxpython again as a way to convert a complex vfp application. An app that is a subset of a db-intensive application but is no more. More of a "grapher" than db business stuff with drag-and-drop interactions. It could and should have been a VB-classic app or as a Delphi one. Happened to be written in VFP for historical reasons.

Since this application is not db-based anymore, no need for business objects, high-grade db connectivity or data-aware controls. I am looking into the sheer wxpython as a an eco-system to deliver the work. Not Dabo.

As the application is relatively intensive in terms of code (over 50 Klines), I am trying to figure out the best way to handle code translation. My current view is to try to initially transfer code with minimal re-factoring and avoid the "early optimization syndrome" as much as possible. Just map the code structure and make it work.

I can easily reuse the same set of win32 libs when necessary including COM and others. And that's a very nice point with Python, it is never getting in the way. But I expect the" translation" to be a tad difficult when it come to two specific points:
-data structures since the current version makes a non-standard use of vfp cursors and its efficient sql extensively at runtime(as a replacement to more sophisticated data structures available within python),
-possibly form building as well since the vfp forms were so easily generated and tested in vfp...

As a wxpyton, and one of the few dabo experts, what would be your take and advices on such a work:)

François