I think you are trying to specify a problem and a solution. You are not going to get an executable in the way you want.
If you simply do not want users to be able to modify the design you can convert the database to an MDE file (see Tools, Database Utilities). You must ensure you retain a copy of the mdb file as you will not be able to alter the mde. The users will need a full copy of Access on their machines.
MDE files have some disadvantages as some actions might be regarded as a redesign. So, for example, you cannot have code that adds buttons to a form. An alternative is to retain the mdb format but totally lock down the user interface so that users cannot see the database window, built in menus or toolbars. It is quite difficult to achieve a solution that would block a serious attempt.
You could try to use a developer edition that allows you to circulate a runtime version. End users do not need Access. I am not current on this but there used to be issues if your machine did not have exactly the same OS as the other users. This was because the runtime package that you distributed picked up all the dll files necessary and these included some that were OS specific.
Starting from scratch you could develop forms in Visual Basic and compile those to an executable. However, you then enter a different world of form design and lose things like Access reports.
