VB Programing support Access Database Microsoft Office VB.Net & SQL Server nev@NevVB.com.au Sydney, Australia (612) 9453-0456 Contact Details 23/02/2012
It 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:
The alternatives are:
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:
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.
VB.Net is now completely stable. Development time is comparable to Microsoft Access – and you will have the best and most efficient 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.
Records will need to be extracted from the current Back-End database, and converted to import into the new Software.