by Jonathan Halder | Mar 13, 2025 | Blogging, MS Access, MS Access Features, MS Access Queries, MS Access VBA Coding
If you want to get the number of records that were updated, inserted, or deleted by your query, you would read the RecordsAffected property on the object that executed your query after it had run. ‘Copied from a normal module ‘We set a reference to the...
by Jonathan Halder | Mar 10, 2025 | Blogging, MS Access, MS Access Features, MS Access VBA Coding
I had a friend ask me for more info about using access files as libraries, so here is some info I gathered up: First off is a link to a file Steve Halder created when researching building our library for our Access JumpStart product. This has a lot of info and sample...
by Jonathan Halder | Mar 6, 2025 | Blogging, MS Access, MS Access Features, MS Access Tables
Today, I remembered a little factoid about Access database versions. You can’t link older front end Access files to newer back end Access files. My mission was to take a set of Access applications I had upgraded for one department (which is being used in...
by Jonathan Halder | Feb 12, 2025 | Blogging, MS Access, MS Access Features
Access is an interesting animal. It’s a Windows desktop app included in the Microsoft Office family originally touted as a low-code no-code relational database management tool. It received decent attention for a while, getting relatively serious new features...
by Jonathan Halder | Jan 29, 2025 | Blogging, MS Access, MS Access Features, MS Access VBA Coding
So the reason I was getting strange behavior in some tests I was running was because there was a third party class which responsibly used an error handling scheme used in it’s tests which required an error being raised with Err.Raise to pass up to the calling...
by Jonathan Halder | Jan 28, 2025 | Blogging, MS Access, MS Access Features, MS Access VBA Coding
I am running into a situation in someone else’s code where an Err.Raise call is not getting handled by any of the upstream calling functions and ends up calling the main VBA system debugger displaying the VBA error dialog. I was trying to recreate the problem...
