When you start out, you probably have a general idea of what you want to achieve but the final product may be quite different. Ideas and opportunities evolve. New functions become evident and additional useful reporting information evolves. If you ask an MS Access developer to quote on a job, they will have to quote high to cover what they and you don't know at the time.
We prefer to quote phase by phase. We can give you a ball park estimate of the whole job but it might be out by 50% or even 100%. After a preliminary discussion, we will quote to do the requirements. Once these are completed, we will quote to do the development. If after testing, you decide on further enhancements, we will quote on those as well. At any time you can walk away and take the work you have paid for. WE will quote for manuals when the development is under way. You get the best price, and we don't have to cover the risk that the job will blow out.
On the other hand, if you want a fixed price quote because that is the way your company works, we can do that too.
![]()
Definitely not. It has a place in any organisation just as Excel and Word. One of the best descriptions I have seen is that in any organisation, there are lots of Excel spreadsheets. They could be developed in a more sophisticated programming language but that would cost 100 times the cost of the Excel solution. For 19 out of 20, Excel works fine and they will last for their life span in Excel. One in 20 may be redeveloped in a more sophisticated language that might even be Microsoft Access.
Similarly with Microsoft Access Development. 19 out of 20 will work just fine in Access. One may be developed in something more robust such as SQL Server and .NET but most do their job in Access. The tens, of hundreds of thousands of dollars are not warranted to redevelop Microsoft Access databases.
Access gets a bad name through people with little programming experience writing poor quality applications. Just as there are badly constructed Excel Spreadsheets, there are many badly constructed Microsoft Access databases. Most are put together by self taught amateurs.
Consider these points when thinking about a Microsoft Access Development.
For |
Against |
|
|
If you would like more information, send us an
email ![]()
.
The following library of Access VBA samples may prove useful for MS Access Developers.
.
![]()