To provide feedback on any of the articles, please enter your name, e-mail address and company (optional) below, add your comment and press the submit button. Thanks
System tables are used by Access to make databases function correctly. With a few exceptions, there is very little information available online about most of the system tables.
The purpose of this article is to summarise known information about Access system tables.
It is also an invitation to other developers to add to this pool of knowledge
Some system tables can be viewed & a few can be edited
However you should only do so ....IF YOU ARE ABSOLUTELY SURE WHAT YOU ARE DOING
Incorrectly editing system tables may corrupt your database or prevent you opening it
This article describes various tests done to compare different approaches to coding:
1. Handling nulls: Trim / Len / Nz
2. CurrentDB vs DBEngine(0)(0)
3. DoEvents vs DBIdle.RefreshCache
Example databases are provided so the tests can be done on your own workstations
If you found this site useful, please consider giving a donation to help offset the costs in keeping it running. Thanks.
This page contains links to some longer articles discussing specific issues in Access in greater detail.
It is intended that the number of articles will be significantly increased in the coming months so please check back again regularly.
SECTION currently not in use
There are many things that developers can do to improve the security of their applications (both design & data). However, no Access database can EVER be made 100% secure. A capable and determined hacker can break any Access database given sufficient time and determination.
The older MDB / MDE file format is FAR LESS SECURE than the newer ACCDB / ACCDE format. Whilst this is hardly news to many developers, I’ve had a few requests to provide more details to justify this statement.