isladogs
MVP / VIP
- Local time
- Today, 03:43
- Joined
- Jan 14, 2017
- Messages
- 18,258
Recently I've been researching the properties of deep hidden tables.
These are special tables that can NOT be viewed in the nav pane even by ticking Show Hidden Objects & Show System Objects
Several of the Access system tables fall into that category BUT not all.
It is also possible to create deep hidden tables yourself (if you know how)
It is also possible to make those tables visible again ....by a different method.
I'm deliberately not going to cover that topic here as my sample database A Security Challenge includes a deep hidden table as part of the challenge
Investigating the properties of these deep hidden tables has rekindled my interest in knowing as much as possible about the Access system tables.
There are at least 29 of these tables in ACCDB files (fewer in MDBs).
Many are created automatically when a new database is created.
Three of those have only recently appeared in my ACCDB files - those starting with MSysWSDP ....
Others are added dependant on certain actions e.g. import/export specifications
Almost all system tables begin with MSys but there are exceptions:
a) USysRibbons - details of user created ribbons
b) f_9E8203D96A754B0890DAF9414007C362_Data (or similar name)
With a few exceptions, there is very little information available online about system tables.
The MSysObjects table is well known & very useful for experienced developers.
I know what some of the others do ... but not all
It is important to stress the main reason for the lack of information
The purpose of system tables is to make databases function correctly
Some system tables can be viewed & a few can be edited
But that doesn't mean you should do so ....UNLESS YOU ARE ABSOLUTELY SURE WHAT YOU ARE DOING
Incorrectly editing system tables may corrupt your database or prevent you opening it
Anyway, having made that point, I'll continue:
The attached database contains details of 29 system tables which I have divided into 4 groups
A: can be made visible / can be edited (but see comment above)
B: can be made visible / read only (though with limited exceptions in some cases)
C: deep hidden but can be viewed using queries - can be edited (but see comment above)
D: deep hidden and cannot be viewed by any method I'm aware of
The purpose of this thread is to try & obtain additional information about the more obscure system tables. Inevitably I'm particularly interested in those in group D.
Particularly by the mysterious f_...._Data table partly due to its very odd name (possibly a Microsoft programmers' in - joke?) and also because its unique in that Access claims it 'doesn't exist'.
I weould also be grateful for details of any further system tables which I haven't seen or therefore listed (as I'm unaware of them)
These are special tables that can NOT be viewed in the nav pane even by ticking Show Hidden Objects & Show System Objects
Several of the Access system tables fall into that category BUT not all.
It is also possible to create deep hidden tables yourself (if you know how)
It is also possible to make those tables visible again ....by a different method.
I'm deliberately not going to cover that topic here as my sample database A Security Challenge includes a deep hidden table as part of the challenge
Investigating the properties of these deep hidden tables has rekindled my interest in knowing as much as possible about the Access system tables.
There are at least 29 of these tables in ACCDB files (fewer in MDBs).
Many are created automatically when a new database is created.
Three of those have only recently appeared in my ACCDB files - those starting with MSysWSDP ....
Others are added dependant on certain actions e.g. import/export specifications
Almost all system tables begin with MSys but there are exceptions:
a) USysRibbons - details of user created ribbons
b) f_9E8203D96A754B0890DAF9414007C362_Data (or similar name)
With a few exceptions, there is very little information available online about system tables.
The MSysObjects table is well known & very useful for experienced developers.
I know what some of the others do ... but not all
It is important to stress the main reason for the lack of information
The purpose of system tables is to make databases function correctly
Some system tables can be viewed & a few can be edited
But that doesn't mean you should do so ....UNLESS YOU ARE ABSOLUTELY SURE WHAT YOU ARE DOING
Incorrectly editing system tables may corrupt your database or prevent you opening it
Anyway, having made that point, I'll continue:
The attached database contains details of 29 system tables which I have divided into 4 groups
A: can be made visible / can be edited (but see comment above)
B: can be made visible / read only (though with limited exceptions in some cases)
C: deep hidden but can be viewed using queries - can be edited (but see comment above)
D: deep hidden and cannot be viewed by any method I'm aware of
The purpose of this thread is to try & obtain additional information about the more obscure system tables. Inevitably I'm particularly interested in those in group D.
Particularly by the mysterious f_...._Data table partly due to its very odd name (possibly a Microsoft programmers' in - joke?) and also because its unique in that Access claims it 'doesn't exist'.
I weould also be grateful for details of any further system tables which I haven't seen or therefore listed (as I'm unaware of them)