Documenting your database - you know you should! Part 1 Whenever I create a new database, it's a bit like starting a new year. I start off with the best of intentions, planning lots of ways in which I'll do things better than last time. It used to be commenting - I'll make sure that [...]
When starting an Access Database design I always like to set the following options which can be found in the code module section in the tools / options toolbar. Tick the 'Require Variable Declaration' tick box, as this removes issues where data can be assigned to a miss spelt variable – many years ago I [...]
I love Microsoft Access. There, I said it. Thare are so many things I love about it that I wouldn't know where to start with listing them all. So, it's just as well that this article isn't about that. It's about fixing one of those things that's just a bit of a pain. Use prefixes [...]
The InputBox is one of the most commonly called functions in the whole of VBA. Whether you're writing a complete database application in Microsoft Access, or just adding bit of functionality to your Microsoft Excel workbooks, the odds are that you won't do much coding before you make your first call to the InputBox function.
So, I thought I'd dedicate this post to getting a little more from the InputBox - particularly in Excel, but also in Access.
Early binding versus late binding in VBA
When you create object variables - that is, variables that refer to an object, such as an ADO recordset, or Microsoft Excel, rather than a data type such as Integer - there are two ways in which it can be done: through early binding or through late binding.
In this blog post, we take a look at what the differences are between early and late binding, when you might use each, and what that difference that decision makes for your code.