Migration from visual fox to java

hm, i wouldnt think so?

could you use JNI as a stopgap solution until you can rewrite it?

Java has excellent DB support.

TuringPesta at 2007-7-29 14:17:26 >

I dont know foxpro, but here are some ideas that may be of help.

Get a foxpro IDE and be able to run the code against its database.

Within the old code, put System.out.println() at each sql statement and print out the sql and the values of all parameters that is sent to/from the database. Next, call up each GUI page and see what sql was called to populate that page. Then click each update button, drop down list, etc for all pages to see what sql is called to carry them out.

Using the above, create a requirement document that specifies what each GUI page should look like and what data from the database tables are needed to populate the page. Also put into the requirement document what type of navigation (hyperlinks, submit buttons) do.

Then hand the requirement document along with a database schema to a java programmer to create the application, independent of the old code. You are far more likely to succeed using this method that mucking with the old code or trying to figure out how it works and how to morph it to java.

The alternative is to look at the foxpro applications and ask yourself if the code base is ever likely to change much and therefore not need much maintenance. If so, just keep the code and live with it.

George123a at 2007-7-29 14:17:26 >