Using Access 2010. Designed a form containing 3 command buttons that open either a form or report. One weeee problem: the buttons don't work/don't do anything. The VBA is there, but it doesn't execute.
DB was imported from one designed in Access 2000, and I kept the format .mdb (did not convert to .accdb because client that uses it has both Office 2003 and Office 2010 in their shop, so dB has to be readable by all). Does that have anything to do with the command buttons doing nothing?
Don, I seem to have heard of this before.
Is it only this one form, or all VBA, if it is all VBA you may have to set a permission to run it.
Have tried adding a new button to see if that works?
Tony: I just found out what the problem was. In the Trust Center, I had changed the setting from "Show the Message Bar. . ." to "Never show the Message Bar. . ." -- the one the pops up when you first open a dB and you have to click "Enable content" to use it. This is just one more irritant in Access 2010, IMO. Not having done much with Access 2010, I thought blocking the Message Bar would relieve users from having to click it, but what it does is make it impossible to use a database until you DO click it once. So I guess you have no choice but to always allow the Message Bar to appear. If that's not true. . . that there's a way to prevent Access from interfering in any way with client access to a database, let me know.
Totally agree. However, over the past 6 months, I've been exposed to both '07 and '10. Both are much worse than previous versions, but '10 is easier to work with than '07.
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Guy
9.9M posts
859.7K members
Since 1998
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!