This is one of those extremely fundamental aspects of any form, adding some easy record search system so users can quickly locate and retrieve a record.
In this article, I thought I’d several techniques that can be used in combination with a Combo Box to retrieve a specific record.
Below, you will find the following approaches:
Continuing on my previous article
Let us now explore taking the code we developed and create a Class Module we can use to subclass our forms with to greatly simplify our live!
Everyone knows the default form navigation buttons
but what if we wanted to create our own controls?
In reality, it is very simple to create our own navigation buttons, so let see how it’s done!
There are a possible number of reasons why you might wish to replace the default navigation buttons:
It doesn’t truly matter why, just that you wish to and that it is possible to do so.
Here are a few samples of what could be achieved:
and these are but a few examples, you can truly customize things as you please, use any text, images, … you wish and make it your own.
Continue reading
Recently I’ve been playing around a lot with Class Modules and Form/Report SubClassing:
and I recently stumbled upon an oddity, a bug relating to an Option Group’s border width property.
Azure, Azure SQL Databases are quite secure and try to limit access to minimize security risks. This, is a great thing. That said, as developers, we often need to remotely access such tools to be able to perform our work.
So how can we do so?
The solution, in the case of Azure SQL Databases, is to create an exception for your IP address in the Firewall rules. Once you authorize your IP address, assuming you have proper login credentials, you will be able to go about your business and connect remotely to that Azure resource.
I recently published an article and video regarding converting form code (module) into a reusable Class Module:
That said, I felt that perhaps, for complete novices to the subject of Class Modules and Microsoft Access Form SubClassing it may have been a little too much, too fast and want to take a step back and try and provide a 101 class on Form SubClassing.
As part of my recent Class Module articles I needed to use a function to validate the existence of form sections:
I thought I’d share a very simple procedure to do just that!
Some people have asked me to cover the subject of Class Modules more, so I thought I’d start by demonstrating how we can take some form code and convert it all over to Class Module so we could then easily implement the exact same behavior on multiple forms with ease by using form Subclassing techniques.
In my last post I demonstrated how we could alter Microsoft Access’ default behavior of always saving any change so that instead it relied on the user explicitly pressing a Save button otherwise changes were not committed. If you aren’t familiar with it, then I’d urge you to quickly review it:
In this post, I wanted to demonstrate how we could take that same code and convert it over to a Class module, or Class modules and show you how easy it then becomes to implement on any form.
One of the biggest issues with Access for novice users is that it is atypical in its saving methodology in the sense that unlike pretty much every other piece of software, it automatically commits changes without user intervention, or even prompting to do so.
So what about making Access behave like most every other application, that is to not have it save changes unless the user specifically asks the system to do so?!
Can we make it so forms employ a Save button, otherwise any changes are NOT committed?
Anyone that has ever created a form with a SubForm has come across the error 3314:
which occurs when one tries to enter data in the subform before the parent record has been dirtied (data entered and assigned a PK which is used to link the subform to the parent form).
Today, I thought I’d share the strategy I like to employ to avoid the issue altogether!
