No Runtime Error-forms or VBA Compile Error when running Function via Button_Click in Form

[byggarebob123]

EDIT: Solution: The check-box "Use Access Special Keys" under File->Options->Current Database was not check. When checked, everything worked as expected!

Hi all,

I have an Access-application where I no longer get any automatic Compile Errors when running VBA-code via the Buton_Click-event in a form. Se the image below for example, when I press the button in the form, the button reacts in the GUI, but then nothing else happens.



I have to open the VBA-windows and choose Debug/Compile Database to see the error. Previously the VBA-window would open automatically and show the error.



If I create a new database with one form and one line of VBA-code, I get the expected behavior, the VBA-window opens automatically and shows the error. Therefore I guess the problem is a setting somewhere within the database itself, and not within the Access-application.



Also, in the same "problematic" Access-application I will not get prompted any Rutime Error-dialogues (not the standard, nor any by an ErrorHandler in the code). However, when opening the Access-database on another computer (same Windows 10- and Access-version, O365 Version 2102) I will get the Runtime Error-dialogues (but not the automatic the VBA Compile Error described above).

I've tried activating warnings with the line "DoCmd.SetWarnings True", but with no difference.

Is there any setting, either in the client or within the database itself that can give this problem? Would really appreciate any help with this since it's quit cumbersome to develop the application on my machine due to these problems!

[Minty]

There are various options that are in the VBA editor.
Goto to Tools¬Options



And under the general tab, see what is selected against a working database on another machine.

[byggarebob123]

There are various options that are in the VBA editor.
Goto to Tools¬Options



And under the general tab, see what is selected against a working database on another machine.

Thank you for the quick reply. Sadly, no difference what so ever between a working DB and my problematic one. The exact same settings on all four tabs.

[Minty]

Hmm, have you tried an office repair.
Or are there any pending updates. I've had some really weird errors when an update hasn't completed.

[byggarebob123]

Hmm, have you tried an office repair.
Or are there any pending updates. I've had some really weird errors when an update hasn't completed.

No pending updates (Updates managed by system administrator) and I've had this problem a couple of months where I know our Office-suite has been updated. Yesterday I tried a complete uninstall/install, but the problem still resisted.

[Minty]

What if you open the database with the shift key - bypassing all code.
Then open your demo form in the troublesome database and see what happens?

Perhaps some setting is being changed somewhere in the opening of your database.

[byggarebob123]

What if you open the database with the shift key - bypassing all code.
Then open your demo form in the troublesome database and see what happens?

Perhaps some setting is being changed somewhere in the opening of your database.

EDIT2: When comparing the settings under Access Options->Current Database of my problematic DB as a new DB I found a difference, the setting "Use Access Special Keys". When activating, I now get auto-compile errors, YES!

Hi Minty!

I did the following, shift key and opening the problematic DB. Created a new form within the DB, added button and an erroneous VBA-code line. Now when I press the button I get the expected result with automatic VBA-debugging, woho!

I have a setting that opens the form "Inställningar" (Swedish for Settings) on start-up, but even when I change that to "none", there seems to be some code running on start-up since it still doesn't work without holding the shift key on startup.



I've looked through my VBA Code and can't find anything running on start-up from there. Any suggestions on where I should look?

EDIT: I have no Marcos (the list is emtpy when I click Database Tools->Macro)

[Micron]

The first situation to eliminate is that the code actually runs. If you knew and said that, I missed it.
The second, in a situation like this is to decompile the db. Plenty of web info on how to do that. The reason for doing so is that the code you see in the editor might not actually be the compiled version, and for whatever reason, it won't compile as written. So you decompile the whole thing then re-compile it as the info will show. That usually fixes this problem. The last thing I'd do for a situation where a single db behaves like this and the others don't is to do any Office repair/reinstall.