Most of my forms are based upon queries. Some of the less used forms on tables. Even for forms based upon queries, I have found with some look-up's from tables, permissions for tables as well as queries are required for all of data in forms to function/show.
One issue which confuses me is for table and query permissions. If you select 'read', 'update' or 'insert' data, 'read design' becomes automatically selected. Groups can therefore as 'read only' open the design of the tables (& save them as new tables) and read query in SQL.
Apologies if I am missing something obvious, but I would have expected to set permissions allowing view, insert & update data but no design features such as 'read design'.
Am I correct in thinking you need to adopt other security measures? Reading many of the posts, I appreciate you can hide the database window, customise toolbars & menus (avoiding the defaults ones in Startup) and not allow the Shift Bypass to work. Therefore - using forms only - there are ways to avoid certain user groups seeing the tables & queries in design view.
One issue which confuses me is for table and query permissions. If you select 'read', 'update' or 'insert' data, 'read design' becomes automatically selected. Groups can therefore as 'read only' open the design of the tables (& save them as new tables) and read query in SQL.
Apologies if I am missing something obvious, but I would have expected to set permissions allowing view, insert & update data but no design features such as 'read design'.
Am I correct in thinking you need to adopt other security measures? Reading many of the posts, I appreciate you can hide the database window, customise toolbars & menus (avoiding the defaults ones in Startup) and not allow the Shift Bypass to work. Therefore - using forms only - there are ways to avoid certain user groups seeing the tables & queries in design view.
