Visual Basic Programmer

Visual Basic Programmer

Access Database Programmer.
Visual Basic.Net Programmer.
Microsoft Office Programmer.


VB Programing support
Access Database
Microsoft Office
VB.Net & SQL Server




nev@NevVB.com.au



Ring me for Visual Basic and Access programming
Sydney, Australia
(612) 9453-0456




Contact Details



23/02/2012

Microsoft Access Database Programmer

Access with a VB6 Front-End

Software Development: Access with a VB6 Front-EndIt seemed a good idea at the time, in the early days of Microsoft Access, to use Visual Basic 6 as a Front-End to an Access database Back-End.

But the advantages of using VB6 as a Front-End have all evaporated, and companies are left with the difficulty of maintaining obsolete software.

The problems are:

  • Visual Basic 6 was released in 1998 and is no longer supported. It was replaced in 2002 by VB.Net. The VB6 software can no longer be purchased.
  • The grid software companies (TrueGrid and Sheridan) no longer exist. Their software is not supported. The software cannot be purchased.
  • The report software company Crystal Reports no longer support their VB6 software. The software cannot be purchased.
  • The Front-End usually has other third-party software, which will be difficult to obtain.

The alternatives are:

Enhance the current system

This is a very, very short term solution.

The system will presumably consist of VB6 code, data grid software and reporting software. Even if the system has been expertly written in well documented modules, it will be a nightmare to support and to enhance.

Supporting legacy software is a "no win" situation:

  • You will have difficulty finding a programmer to maintain the system.
  • New Windows operating systems or updates will eventually cause grief with VB6 and the other software.
  • There will be no support.

Convert the Front-End to Microsoft Access

This is the Mini-Cooper option. Microsoft Access will allow reasonably fast development times. The result will not be quite as slick as the VB.Net software option, but reasonably acceptable and reasonably fast to develop.

Development should be done in phases. The new system can work in parallel with the legacy system – until the functionality is completely replaced. It is unlikely that much business logic will be extracted from the legacy system.

Note that Microsoft Access will need to be purchased for each user.

Convert the Front-End to VB.Net

VB.Net is now completely stable. Development time is comparable to Microsoft Access – and you will have the best and most efficient software.

Purchase off-the-shelf software

It is highly unlikely that any one software vendor will be able to replace all the functionality of a custom built system. Products like MYOB could handle the accounting requirements. Additional third-party software will most likely be needed to handle other aspects of the legacy custom software.

Everything depends upon the fit, and how easy it is to customise the third-party software to a Company’s requirements.

  • Business processes will need to be changed to fit in with the third-party software.
  • Staff will need extensive training, or more likely, trained staff will need to be hired.
  • Constant (and costly) upgrades will be needed.
  • It is likely that most of the software features will never be used.
  • I have yet to find accounting software that users are happy with.
  • It could prove to be a very costly exercise.

Records will need to be extracted from the current Back-End database, and converted to import into the new Software.


Home Page         Next Page