🚀 go-pugleaf

Unfortunately (maybe really a Good Thing) there is no conversion utility.  
The conceptual difference between Java's pure OOP and Access is so great 
I don't think the code would port well for anything except the most 
trivial application.  OTOH redeveloping shouldn't be too tough, you 
already have the logic and business rules established and it does give 
you an fresh look at the best UI design.  

The other killer is the method of creating UI layouts - Windows uses 
absolute x-y coordinates, Java uses a more or less platform independent 
layout scheme (which might cause you a few headaches until the penny 
drops and you use the functionality instead of fighting it).

As a point of interest, you may find (untested) that you can connect to 
the existing Access database to test at least the basic concepts with a 
Java UI.  However,  Access uses a non-standard syntax for SQL and syntax 
which works in Access might fail after you port to a different database 
host.  Also be aware that the Access-Jet combination is not the most 
robust in the world when faced with networked multi-user projects.  I 
think you already have it in mind to migrate to a more reliable platform, 
so I am only confirming this as a good idea.

In article <7ese8a$aql20@forums.borland.com>, itg@turk.net says...
> I understand that the data needs to be exported from
> Access DB and imported to a new database. How about the code? Is there a
> tool. You say that code needs to be redesigned. Does that mean rewritten?
> Is there a tool?
> 
> 

-- 
pf