###Technical Articles###

* [Changing the colour scheme programmatically][2]
Allow your users to change the Office 2007/2010/2013 colour scheme from within your Office applications.
_Last Update 01DEC2014._

* [Enhanced Message Box Replacement][4]
A drop-in replacement for the standard messagebox that offers many enhancements, including the ability to display rich, formatted text.
_Last Update 21OCT2014._

* [VBA: Unicode Strings and the Windows API][13]
We examine what happens when sending VBA Strings to the WinAPI and find some solution to avoid their unexpected mangling.
_Last Update 01OCT2013._

* [using .Net strings in VBA for fun and profit][12]
Format VBA strings the .Net way!
_Last Update 12SEP2013._

* [VBA for 32 and 64 bit systems][11]
Make your code future-proof for all versions of Access, old or new!
_Last Update 07JUL2013._

* [Checking blank variables][10]
A useful function to help test for ‘blankness’ of a VBA variable that could be Emtpy, Null, Missing, Nothing or an empty string.
_Last Update 09SEP2009._

* [Run-time Error 3155 ODBC insert on a linked table failed][9]
Correcting this strange MS Access error when using SQL Server and nvarchar fields larger than 255 characters.
_Last Update 11JUN2009._

* [Access vs SQL Server: some stats (part 1)][8]
Getting some baseline statistics about the performance of SQL Server vs MS Access on inserting records with autoincrement integer or GUID Primary Keys.
_Last Update 16APR2009._

* [Building ‘upsizable’ applications][7]
A few simple rules that will help making your Access application future-proof and allow it to be upsized to SQL Server with minimal pains.

* [Upsizing to SQL Server 2008][6]
Don’t use the _Upsizing Wizard_ provided in Access when you need to move your database to SQL Server. Use the free Microsoft SSMA instead!
_Last Update 17MAR2009._

* [Checking network paths without freezing your application][5]
Checking for the existence of network files or folders can be a pain in Access: it can take 30 seconds if the path cannot be reached during which your application will freeze and appear unresponsive. In this article I present a easy way to check for these troublesome paths without slowing down your application at all.

* [Restarting the database programmatically][3]
Restarting the database from code used ot be a pain, now it’s trivial.
_Last Update 13FEB2009._

* [Modal Dialogs with transparent background][1]
As a follow-up to an article on the Access Team blog, show those important dialog boxes on top of a dimmed background.

[9]: /2009/access-run-time-error-3155-odbc-insert-on-a-linked-table-failed/
[8]: /2009/access-vs-sql-server-some-stats-part-1/
[7]: /2009/access-building-upsizable-applications/
[6]: /2009/ms-access-upsizing-to-sql-server-2008/
[5]: /2008/checking-network-folders-without-freezing/
[4]: /2008/ms-access-enhanced-message-box-replacement/
[3]: /2008/ms-access-restarting-the-database-programmatically/
[2]: /2008/ms-access-changing-the-color-scheme-programmatically/
[1]: /2008/ms-access-modal-dialogs-with-transparent-backgrounds/

###Why Access?###
I’ve been working with MS Access for a few years now. Until then I had done everything in my power to stay away from this “Frontpage of the database world” as I liked to call it.

My hand was twisted when a customer wanted some basic ERP system that had to be implemented in Access since he wanted to keep some amount of control and it was the only sophisticated tool he knew how to use as a Manager.

It’s been an interesting journey so far. Access is one of those products that you love to hate.
After a while I had to rescind my view: it’s actually a very useful rapid application development platform that bridges the gap between pure database and pure GUI interface.
It’s not always elegant, and parts of it are showing their age (VB6 IDE, inconsistent VB syntax, less-than-glamorous controls) but Access 2007 has brought plenty of refinements that are keeping Access relevant today (ribbon, support for transparent images, theming and colour scheme, XP-styled controls, improved extensibility though Sharepoint and slightly better support for .Net).

Access gets a bad rap because the vast majority of its users are not professional developers: most people are power-users and managers and use Access as a simple tool to get the job done.
The resulting applications are functional but just looking at them is a hair-raising experience to a developer.
This doesn’t mean you cannot develop proper applications using proper coding standards. There are lots of talented Access programmers building professional solutions that solve real problems.

In this blog I share some of the titbits I created and knowledge I learned in the hope it will be useful to others.

*[ERP]: Enterprise Resource Planning software.

Last modified: Sunday, 28 October 2018


Write a Reply or Comment

Your email address will not be published.