VBA Command Buttons not working (1 Viewer)

[kevnaff]

Hello All.

I work in a hospital and have been working on a .mdb/.mde using Microsoft Office 2010. We are eventually upgrading to Office 365, which means I have to upgrade the database to a .accdb/.accde. To do so, I created a blank database and imported over all objects in to a new .accdb. Since doing so, none of the command buttons work in the database. When I click any command button, nothing at all happens.

When I create a new command button, I get the following message:

After the message appears, it does create a new command button. If I copy in the VBA code from any command button in to the code builder, nothing happens. However if I use the macro builder to do a simple open form, it works OK.

Any ideas as to why this may happen?

Below are my references:

Thanks in advance for your help.

 

[arnelgp]

on the "new" button, can you select Code Builder, when adding code
then paste the code from the .mdb button?

 

[pbaldy]

See if this helps, the database should be in a trusted location.

You can't open any Access wizard - Microsoft 365 Apps

Describes a problem in which you receive and error message when you try to open a wizard in Access 2007. This problem occurs when you have the Disable Trusted Locations and Disable all macros except digitally signed macros options enabled.

docs.microsoft.com

 

[arnelgp]

are you sure the Original mdb was in created in A2010 or you are just opening it in A2010 before?
coz i just downloaded an mdb created in A2010 and the
conversion went without problem.

 

[kevnaff]

are you sure the Original mdb was in created in A2010 or you are just opening it in A2010 before?
coz i just downloaded an mdb created in A2010 and the
conversion went without problem.

Hi Arnel,

I copied the code from the .mdb on to the new button and nothing happens when it is clicked.

The mdb was likely created in Access 2003 or earlier. At some point I think the .mdb may have been imported in to an access 2010 .accdb blank database and then saved as a 2003 compatible .mdb.

Thanks

 

[kevnaff]

See if this helps, the database should be in a trusted location.

You can't open any Access wizard - Microsoft 365 Apps

Describes a problem in which you receive and error message when you try to open a wizard in Access 2007. This problem occurs when you have the Disable Trusted Locations and Disable all macros except digitally signed macros options enabled.

docs.microsoft.com

Hi,

Please see below what the trusted locations settings are set to:

The option to add a new trusted location is greyed out.

Thanks

 

[pbaldy]

You're definitely missing the wizard location plus of course the location of the db. Is there an "Enable Code" button in a bar below the ribbon?

 

[MajP]

To do so, I created a blank database and imported over all objects in to a new .accdb. Since doing so, none of the command buttons work in the database. When I click any command button, nothing at all happens.

In design view when you look at the .onclick property of the buttons do you see "[Event Procedure]"? If this is blank you need to add it back in. You can do this by pasting it in, pulling down the dropdown, or click on the ellipsis.

 

[kevnaff]

You're definitely missing the wizard location plus of course the location of the db. Is there an "Enable Code" button in a bar below the ribbon?

There is nothing showing beneath the ribbon unfortunately.

 

[kevnaff]

In design view when you look at the .onclick property of the buttons do you see "[Event Procedure]"? If this is blank you need to add it back in. You can do this by pasting it in, pulling down the dropdown, or click on the ellipsis.

Please see below:

All of the code is there when I click on the 3 dots to go to the VBA screen

 

[MajP]

All of the code is there when I click on the 3 dots to go to the VBA screen

That was not the question. The question was if the word "[Event Procedure]" was already there? Or did it appear after clicking the ellipsis?

 

[kevnaff]

That was not the question. The question was if the word "[Event Procedure]" was already there? Or did it appear after clicking the ellipsis?

Sorry Maj, yes the Event Procedure was already there.

 

[kevnaff]

Update:

So I had previously imported the .mdb in to a new blank database in Access 2010. However I never put this in to use. I have imported this .accdb in to the new version of 365, and the command buttons are now working OK.

The references and trusted location are still the same, so I'm not certain what was causing the problem.

I am going to import the most recent .mdb in to access 2010, saved as a .accdb, and then import this in to Office 365. Hopefully this will all go well

 

[MajP]

Sorry Maj, yes the Event Procedure was already there.

The reason I asked this question (although no longer relevant) is that you can have event procedures in a form (such as a button_click), but if the event "onclick" property does not have "[event procedure]" there is no contract between the procedure and the event that caused it. The actual click action will not cause an event to be raised and thus the procedure has nothing to trap.

This can happen when you copy and paste code from one form to another. You will see the event procedure in the form, but the Event itself is not registered. I do think this is fixed in A 2016. I noticed if I paste code in the form the events are registered with "[Event Procedure]"

 

[kevnaff]

The reason I asked this question (although no longer relevant) is that you can have event procedures in a form (such as a button_click), but if the event "onclick" property does not have "[event procedure]" there is no contract between the procedure and the event that caused it. The actual click action will not cause an event to be raised and thus the procedure has nothing to trap.

This can happen when you copy and paste code from one form to another. You will see the event procedure in the form, but the Event itself is not registered. I do think this is fixed in A 2016. I noticed if I paste code in the form the events are registered with "[Event Procedure]"

I see what you mean. As far as I can see, all of my command buttons still have the [event procedure] in the onclick property.

 

[kevnaff]

Update:

So I had previously imported the .mdb in to a new blank database in Access 2010. However I never put this in to use. I have imported this .accdb in to the new version of 365, and the command buttons are now working OK.

The references and trusted location are still the same, so I'm not certain what was causing the problem.

I am going to import the most recent .mdb in to access 2010, saved as a .accdb, and then import this in to Office 365. Hopefully this will all go well

So forget the above. I opened a version of the database that worked completely fine. I closed it, and now I've no idea what copy it was that was working OK. So I am back to square one.

If anybody has any tips that would be great.

Thanks

 

[MajP]

The fact that "[Event Procedure]" exists seems to suggest a problem in the compiled code. Only thing I can guess. When you convert it, it is not compiling correctly. I would do a full decompile, recompile, compact and repair.

Access Keeps Crashing when I go click Debug

Hi, I have just been working on Crosstab queries and reports with parameters and have got it all working (or so I thought). I am now getting an error on the Querydef function where I am setting up the parameters of the query in VBA before calling the report. I have no idea why this isn't now...

www.access-programmers.co.uk

 

[Pat Hartman]

Although converting as you did is not wrong, there is an easier method.

Open the .mdb
Open any code module and compile the db.
Fix ALL compile errors
Save
then save again using the save as .accdb option.

This copies all the settings as well as all the objects.

 

[MajP]

I would do the above and do the conversion, and then still copy all objects into a new accdb. I would then still decompile just to be extra safe. (That is suspenders and a belt).

 

[kevnaff]

Although converting as you did is not wrong, there is an easier method.

Open the .mdb
Open any code module and compile the db.
Fix ALL compile errors
Save
then save again using the save as .accdb option.

This copies all the settings as well as all the objects.

Hi Pat.

I opened up my stable .mdb that I know is the latest version we are using. I open the VBA editor using ctrl + g. The option to compile under the debug option was greyed out.

I then saved the .mdb as a .accdb. Opened the .accdb and compiled the database. This was all done in Office 2010, and it all works OK at this point.

I then open the same.accdb in Office 365. I compiled the database again. It opens as normal, but then the command buttons do not work.