Command Buttons on older version of Access

[Ceadmo]

I have an old 2003 Access database and when I opened this database in 2010 Access the Command Buttons won't work. Everything else seems to work just fine. Is there a quick fixed for this problem or do I have redo all of the buttons by hand one at a time.

[June7]

Bing: access 2003 command buttons not working access 2010
http://answers.microsoft.com/en-us/o...b-3db25b0f3cd4

[Ceadmo]

As far as I can see I have disable the items in the TGrust Center, but my buttons still do not work.

[ItsMe]

... but my buttons still do not work.

When they did work, what caused them to work? Did they use embedded macros or did they use VBA?

[Ceadmo]

When I originally set the buttons, I would have used the build in wizard to set them up.

[ItsMe]

Then there should be VBA behind the form for each of the controls.

Check your original copy of the MDB and compare the VBA with your new 2010 version (use the View Code option). I cannot think of a reason why the old VBA generated by the wizard would not work for a command button. There are some exceptions for controls like option groups.

[June7]

Just tested creating a new button on form and let wizard do the coding. Even though I have db set to 'always use event procedure', it builds an embedded macro. However, when I double click in an event property, I get [Event Procedure] but no code is generated.

[ItsMe]

I don't have a keyboard or monitor connected to me XP box with A2003. So, I probably won't get around to testing it. The way I remember 2003 working is it will generate VBA from the Wizard. Things like opening a form and applying where criteria is done via VBA and no Macro. I do not recall any special settings for generating a macro vs VBA. Maybe I never paid attention.

Anyway, if there is not VBA in the original DB, the OP can look for a Macro and or import the form using the Advanced Options of the Import Wizard, to include macros (can't remember what the option reads like, exactly).