>Exactly what we're going through here, Michel.

Could you rephrase the question?

>This is what's going on here, too. Personally, I like the VFP/VB front-end
>and MySQL on the back-end, with MySQL killing two birds with one stone: It's
>a RDBMS, and there's tons of support for scripting languages, such as PHP
>and the like.

Yes, I heard a lot of good things about that.

>In days gone by, I worked for a company called "Interactive Digital Devices."
>Basically, we designed mil-spec (practically) joysticks, rudder pedals, etc.
>for the video game industry. Lockheed Martin, General Dynamics, Boeing, G.E.,
>Bell, and NASA wound up being our best customers :^). One of my duties while
>working there was to disassemble 3D flight-sim apps that used only digital
>joystick routines (for the Amiga), and then I would patch them to use our
>analog products, with all of the patch code being applied to the app in memory.
>I had to disassemble hundreds upon hundreds of thousands of lines of other
>peoples code, and then figure it all out in reading assembly generated with
>C compilers. Now _THAT_ was a pain! :^). So, reading other peoples VFP code
>is a cake walk; however, it is still very time consuming, especially when you
>think you can rewrite the code faster.

Yes, but one point about redoing the application is that we have to go back to square one when comes time to start the testing phase.