Here’s a hidden gem for any serious developer that doesn’t seem to get enough of a spotlight.
… and no this is not an article about creating a library database to manage you collection of books, CDs, DVDs, …
What is a Library Database?
A Library database, also sometimes referred to as a Code Library, Code Db or Reference Library, is a standard Access database (which can be compiled to secure it from prying eyes) that enables one to create an easily deployable, reusable, maintainable library of objects and code to implement within any other database.
Huh? What does that mean in plain English?
Simply put, when you start a new project, typically, we go around scavenging code modules, forms (dialogues, date picker, progress bar, …) and the likes from different sources to import them into you new project to give us our basis to start building our application?
This is where a Library database can come in.
With a Library database, you place your common code components (Date/Time, Validations, APIs, …) and other objects (Date picker, Progress bar, …) and then simply reference it within your main database so you can use them seamlessly.
Continue reading

Although this is functional, let’s face it, it is less than ideal! Continuously having to scroll down to the bottom, or even having the new row hidden completely out of sight does not enhance the user experience. Furthermore, if you apply default values to your controls it can end up confusing your users as they will think they are actual rows of data rather than a row for performing data entry.
