[Solved] Stand Alone Form and hiding the db container

[gkick]

Stand Alone Forms and Hiding Base Container
No problems with Hyperlinks to open forms but how does one close the form calling the other form as there only is one Action within the properties box?
I am missing something - Frontend Backend approach less potential dataloss and reduced need for macros the frontend being stand alone forms. Thats fine, the database container is not visible from within Writer, however can easily be accessed via file open base ?
Guess one could change the odb s file attributes to hidden as a non foolproof bandage or is there another option?
Also attempting to eliminate macros where possible and wonder if there is a way to run update, delete, append and create queries without macro and without going to Tools SQL ?
Thanks for any ideas

[Villeroy]

You have a backend database where you can set up privileges in SQL (keywords CREATE USER, CREATE GROUP, GRANT).
You have office documents as frontend which can be made read-only. The Base document stores the connection parameters and various definitions of queries, forms and reports but not a single byte of user data. You can write protect stand alone form documents as well. The form controls will work anyway since they write to the database rather than the containing document. If you use spreadsheet reports (like I do), these need to be writable because the imported data modify sheet cells.

[gkick]

Thank you !