• Skip to main content

WorkSmart Database Masters, LLC

Eliminating software inefficiencies

  • Services
    • Database Development
    • Mobile App Development
    • Business Intelligence (BI)
    • Internet of Things (IoT)
    • Custom Training
  • Qualifications
    • Microsoft MVP
    • Microsoft Silver Partner
    • National Speaker
    • Customer Testimonials
  • Resources
    • Programming Groups
    • Vendor Partners
    • Free Access Book
    • Free Productivity Software
  • Employment
    • Experts Only – Apply Here
  • About
    • Team Members
  • Contact Info
    • Contact Form

Jul 24 2014

Stay Clear of Access Programmer ‘Cheetahs’

Integrity isn’t found in all Access developers. Unfortunately, many stalk companies like prey, spreading fear and weakness. So, how can you tell the good ones from the bad? Here’s how to spot a programmer to avoid.

1. Make Sure You Keep the Control

Some programmers will “encrypt” an Access database, making it so you cannot make changes to forms, reports or other objects. You can tell when this occurs if your database file is an .mde instead of an .mdb file, or an .accde file instead of an .accdb file. If you only have an encrypted copy, you can never make any design changes to the database.

How to protect yourself?
Insist that you always have a current copy of the .mdb or .accdb file. If you are unhappy with the programmer or they are no longer able to support you, you can hand a new programmer a copy of the editable database.

2. Watch for the ‘Bait and Switch’

Be careful of database designers which quote a low ballpark figure in order to win a project, but then charge a much higher amount. This can occur because there wasn’t anything in writing stating what will be accomplished for a specific amount.

How to protect yourself?
For every project phase, get a written Statement of Work (SOW) or Project Scope of what will be accomplished, before agreeing to the development. They should include the tasks to be accomplished as well as specific functionality that isn’t normally included in database development (i.e. manipulating an Excel spreadsheet using code or creating a traibning manual.

3. Require that they Document their Work

You may not realize it, but if a programmer is adding some special functionality, they have the ability to insert comments on what that functionality is used for and hpw it works. If they don’t do that and have to make changes in the future, it makes it difficult for them to remember what they did. Also, if another programmer takes over, they have to take more time in order to figure it out.

How to protect yourself?
Just make sure that your requirements include that they add comments & document fields/features whenever necessary.

4. View Their References and Endorsements

With social media such as LinkedIn.com, you have the opportunity to view a developer’s profile and look at the Recommendations listed. Customers aren’t going to give positive feedback if they did poor work. I have over a dozen recommendations on LinkedIn and more than 95 people have endorsed me for Microsoft Access.

How to protect yourself?
Be proactive and take a look. The best developers have open LinkedIn profiles and encourage you to view them. btw – want to see mine? Check out http://www.linkedin.com/in/andytabisz

Andy Tabisz, MCAS, MOS is owner and lead innovator of WorkSmart Database Masters, LLC, a Michigan-based development firm serving customers nationally.

Written by Andy Tabisz · Categorized: Blog Posts

  • LinkedIn
  • Microsoft MVP Info

COPYRIGHT © 2025 · WORKSMART DATABASE MASTERS · Michigan Home Office: 616-466-4393