un-running vb code in executable access file

[simon d1]

i created a database access which involve navigations and button with vb codes.
after I convert it to executable file, it was working properly. but the moment I close it and run it again, all the navigation and button will not respond according to the command (vb codes) also timer will not work. but the original file (non executable) is working properly when open. am using access 2013

[jforbes]

I'm familiar with creating a compiled (.mde or .accde) Access database and a lot of people refer to this as an executable, if this is not what you have done, please enlighten us.

The following is assuming you are using a compiled database: It sounds like you are having a trust issue. (that sentence made me laugh) I would first make sure the path to the database is in the trusted locations list in the Trust Center. The path will need to be setup for every user, on every computer, as this list is maintained on a per user basis. Most likely the path you used to develop is in this list, if it is, you can test this scenario by copying your compiled database to the same directory and attempting to execute it, and expect it to work.