Front-End for MS Access migration? [closed]

Answer 1

I have a different perspective for you to consider. Your main issue is that it hides logic and there is data and applications scattered through the organization.

Unfortunately I don't know of a RAD (rapid application development) tool that is as easy as Access to create functional forms.

However I would recommend that you focus more on the possibility of centeralizing your data and logic and still allow Access as a front end. I support a database product called Advantage Database Server which supports RI (refferential integrity) rules, stored procedures, triggers, etc. that can all be managed on a centeral server thus bringing all of the logic to you. These Access front-ends could then link to the data backend using ODBC or OLEDB. If you switched to a solution like this then later down the road you would have flexibility to write other applications such as .NET, PHP, JDBC, etc. that tie into the same data while phasing Access front-ends out.

A good start would be to stop new Access development unless they're using this sort of data backend.

Answer 2

Out of the 1000's of Access files how many have you been asked to support? I'm guessing less than 100. Why rebuild an application that A) no one uses B) works fine just the way it is?

You need to begin a policy that it is an acceptable practice for a large organization to develop custom applications in a robust, scalable, reliable, yadda yadda yadda environment. Identify the Access applications you feel are critical or are being outgrown and just work on those.

Be prepared to handle the expectation of getting their quick and dirty little applications on a quick turnaround. You'll have to show them the benefits of your new apps.

I think you just need to be a resident expert and teach these users how to improve their application or get your input from the beginning to start them off right. The requirements to convert all of these files would otherwise be overwhelming.

Answer 3

Is there anything that will replace the front end part of MS Access?

Maybe Kexi?

Answer 4

You can also take a look at Firebird

Here is the way to migrate (you need Delphi)

I also find this MDB2FDB

Answer 5

Microtools offers Access Whiz, a set of Access conversion tools. It consists of Access to ASP .NET (VB/C#) converters, Access to VB6 converter, Access to WinForms (VB .NET/C#) converters and Access to Crystal Reports converter. More information and trial demos can be found at http://www.microtools.us.

Answer 6

You could check out Oracle's Application Express. It's free and it's geared toward Access developers.

It has a migration assistant as well that you run your Access database through, it proccesses the data and the forms, migrates everything to an Oracle Database (this works with the free database, Oracle XE, and comes install by default) and builds web forms for your Access database.

So in the end you'll have your Access databases on the web, your data in Oracle and somewhat nice web front end for extending them.

As far as Oracle goes, the tool isn't half bad. You can sign up for a free instance to play around with here.

Here's the document that explains how you migrate Access Databases.