What can I do with it?

What can I do with it?

Ok, so what can I do with Mediator and its Delphi components?

There are many possibilities here. The option which is most interesting for you will probably depend whether you are Clipper/xHarbour developer of Delphi-only developer.

Delphi developers

a) Use Mediator Delphi components to quickly migrate your ISAM-based applications to SQL database environment. In most cases, all you need to do is replacing your BDE (or similar) components with corresponding Mediator components. Move your DBF, Paradox and FoxPro applications to SQL in no time! Forget about rewriting all of your application code to SQL - Mediator will do it for you in quick and efficient way, resulting in a new scallable application working with SQL database.

Mediator Delphi components facilitate migration from any ISAM-based data access components based on TDataSet component. This includes the following solutions:

·BDE local databases - DBase (DBF), Paradox, FoxPro

·DBISAM Database System (TM)

·Advantage Database Server (TM)

·NexusDB (TM)

·Apollo (TM)

·TurboDB (TM)

b) Use Mediator Delphi components as BDE-replacement for developping DBF-based applications. This is completely free.

For xHarbour and/or Clipper developers.

a) Use Delphi and Mediator components as migration path for your xBase applications. You can gradually migrate your applications writing new modules in Delphi. Thanks to xHarbour kernel underlying Mediator components, your DBF and Mediator data is accessed in 100%-compatible way from both xHarbour and Delphi applications.

It is hard to belive but now you can even integrate your xHarbour code with Delphi application! All you need to do is to put your xHarbour code into DLL file and then run it from Delphi application passing required parameters!

b) Use Delphi and Mediator components as high-grade RAD environment for developping new GUI modules extending your existing xHarbour/Clipper applications.

c) Use Delphi and and Mediator components as GUI for your xHarbour code kept in DLL files.