{short description of image} Expertise


{short description of image} Delphi

When developing a system that is to be distributed to multiple users or requires fast and robust operation in a Windows or Internet environment, my first choice is to use Borland's Delphi.

MVSCL were selected by Borland in early 1994 as one of 500 worldwide users to participate in the beta test program for Delphi, this culminated in a Borland run training course in Sydney which I also attended. I was chosen to participate in these programmes because of our previous extensive use of Borland Pascal and Paradox in the DOS environment.

Delphi was first released on the New Zealand market in March 1995, and has grown to rival all of its competitors - there is no Rapid Application Development tool that comes near Delphi for runtime speed of applications.

Most RAD tools are designed primarily as database tools. Delphi, while as good as other tools for database applications, has the advantage of not needing to be associated with a database; we have developed many applications that do not have any database associations, I have also developed many applications that are database applications.

The key advantage to using Delphi as opposed to other products such as Microsoft Access is that as requirements for the system become more complex over time I often find that products such as Access simply "run out of steam" and a full system redevolpment becomes necessary; with Delphi I have never had that situation arise.

Many larger corporations today have a "Microsoft only" policy, what I am finding is that by using an Access database accessed via OLEDB that I can still fall within such a policy even though the application is written using Delphi. I now rarely use Paradox as an underlying database, preferring to use MS Access via OLEDB.

Delphi is now taught in most Polytechnics and University courses and the pool of development resources is now readily available.

{short description of image} Microsoft Access

I am being increasingly called upon to maintain existing systems written in Access.


{short description of image} Paradox

I have in the past worked extensively with Paradox, although no longer used as a mainstream product I am still called upon to maintain existing systems.


{short description of image} Pascal

As with Paradox this is no longer a mainstream development language in the Windows environment, but again I am occassionly called upon to maintain existing systems.

Return to Home Page