Ehtisham Rasheed, Sialkot, Pakistan:
i'll first break down the whole project into parts and after completion of each part i'll get confirmation from the client... this saves lot of money for client and time for development...
i can further explain this procedure during Skype session, if u need more clarification...
Christian Koch, Berlin, Germany:
I developed a front end system. After setup you can access your data with all important functions you need.
Mark Horner, Bristol, England:
As I have done databases of this scale and size before, it's extremely likely what you want done I have experience in doing, and some of that code will be available to me to re-use by having it on my personal laptop from freelance projects. This enables me to chop and change code where possible rather than write everything from scratch which can take longer, and cost the client more money.
Further to this, I don't mess around and give unrealistic deadlines, if based on the spec I think it will take me 3 months to get a working copy out the door to you I will tell you that upfront as honesty is the best policy. I would never over estimate and under deliver just to get an extra few hours pay as I would class that as deceitful.
Lastly, I always look for ways to improve and I do enjoy reading up on new theories and techniques, by browsing forums and checking solutions to people's problems. As you never know when the solution may be something you require whether it's on a personal or professional project.
Ven Grollmus, George Town, Tasmania, Australia:
I spend time with the client at the outset to understand what they need to achieve with the system, document the processes and requirements and then come up with an agreed solution and pricing strategy.
This reduces re-work down the track, which can delay the project delivery, and the chances of key functionality being forgotten or missed.
I give a quote on the final product to be delivered, which means that the client knows what the project will cost, and when it will be delivered. Depending on the length of the project, then payment plans can be implemented for certain deliverables, which ensure both parties know what they will be receiving and when and not overly impacted by cash flow issues that can occur in large projects. This ensures that the client can afford to have the project completed in their own time-frame, and when they can afford to have each deliverable completed.
Bruce Bray, Phoenix, Arizona:
I think the biggest two advantages I have are that 1) I have been programming in Access and VBA since the very beginning, so I have already been through the trenches, and 2) I have a complete understanding of how Microsoft Technologies work together.
I am a complete MS Access / VBA / MS Office / SQL Server developer. I have been working with MS Access all the way back to the days of 16 bit software. I have built numerous databases for county governments and small businesses in the state of Arizona. I have complete expertise and can code with ease in modern current MS Office applications. I have built the kind of system that you are speaking several times. I can also hook your MS Access database up to a SQL Server database, if that is what you desire.
Yuriy Sultanaev, Ufa, Russia:
The most valuable resource is time
Savings on software - is the extra hours of work others employees
Temitayo Ilori, Berea, Ohio:
Taking time to create database architecture helps prevent the problems of data redundancy and inconsistencies, which constitute a waste of time and money.
Julie Hogue, Akron, Ohio:
I believe that it is critical to know about future modules or plans for the software before development begins. This allows me to provide expansion capabilities within the software for future uses. For example, if you plan to integrate your new software to an accounting system, I would like to know in advance so that I can be sure GL Account numbers are available and the links between the different systems are compatible. If the customer ID is numeric in the new software but the accounting software has a text identifier, a future conversion of the data could be avoided by planning in advance.
Biju John, Pathanamthitta Dist., Kerala, India:
* Ask client the exact requirement
* Study it properly.
* Make list of objects
* Send the details to the client and confirm with the client the requirement
* Design the database in a properly structured manner
* Make room for enhancement without affecting existing setup.
* Make provision for dynamic setting of criteria wherever possible. This saves modification times.
Grace Elaiza Seballos, Davao City, Philippines:
First and for most, gather and analyze what my clients needs. I already have my own standard architecture. I no longer need to think about that. It has been tested over and over again since 2005, in different types of systems for different types of industries. I created this architecture so I can focus on these 8 tenets (in which I believe that you should also be looking for. Expert level skills are easy to find. But an individual whose skills were tested and tempered are more worth having) .
1. Systems should be able to improve communication, so you can make better decisions.
2. Systems should be able to increase productivity, so cost and time can be saved.
3. Systems should be able to improve customer service. This will give you happy customers.
4. Systems should be able to reduce stock outs, so you can increase sales. (should your system include inventory)
5. Systems should have an efficient collection process, in return, you get an increase in cash inflows.
6. Systems should be able to optimize inventory levels, and therefore, decrease your tied-up capital.
7. Systems should be able to monitor costs and expenses, in order to maximize the profits.
8. Systems should be able to give you less time in managing your business, so that you can have more time growing it and yourself.
Artiben prashantbhai S., Bhavnagar, India:
As I said, using the relational tables we can avoid repeated data entry and will save time and/or money
Same is with the use of combo boxes.