When this thread was started, I found the idea interesting but like most of those responding, I couldn't think of a practical use for it.
However, I have been able to make use of the idea as a way of protecting the data in tables and queries from users who know enough to be 'dangerous'. i.e. those users who are able to circumvent simple Access security and, in some cases, cause damage by 'meddling'.
My new article demonstrates one way of helping to protect the data in tables and queries from unwanted modification by making them read only.
This is surprisingly easy to do and the method used allows the same data to be made editable in forms as required.
End users should only view data using forms. However, knowledgeable users may know how to circumvent basic security and access/edit/delete data from tables. This article demonstrates one way of protecting tables and queries from unwanted modification.
www.isladogs.co.uk
The article includes an example app and a short video (no audio commentary) to demonstrate the idea