OK I'll go ahead and ask the obvious......

If tools exist that are optimized to work with and design forms for the Palm OS, why would I bother going through all of the trouble? Is the primary reason so that I can retain the use of a language that I already know? If so, it opens up an interesting debate. Do you:

1. Continue to use the same language for everything because it is the one you know, not because it is the optimal tool for the job...

or..

2. Decide that cost benefit analysis yields that it is better to take the time to learn a new tool because the productivity in the long run will be greater...

From a programming ego standpoint, I certiainly understand where you are coming from. It is nice to not let the "bastard" get you. The fact that you beat the odds and did something that either you or everyone else did not think could be done.

From a business standpoint however, a laundry list of other concerns would exist for me. By your own count, it took quite a bit of effort. Since VFP was never designed to do this sort of work, it begs the obvious question of "Sure it can be done, but would I really do this???" What limitations are imposed? Depending on the extent of the limitations, what are the prospects of recouping the initial development costs???

I am probably looking at this issue too deeply. However, it is a good illustration of the phenomenon that exists in the VFP development community - use VFP because it is the language you know, not because it is the correct tool..