Re: Command Button Wizard

I don't know the answer to your questions. I was just trying to help you find the place to check Macro security. If Security is not on the Macros sub-menu you may be able to place it there as follows:
Click Tools > Customize. Select the Commands tab. Select Tools on the left-hand menu, and find Security on the right-hand menu. Drag Security to Tools (don't let go yet) on the menu bar. When the drop-down menu appears, drag it to Macro, then drop it in the sub-menu when that appears. Close the Customize dialog box. Security should now be available on the Macro sub-menu.
I am basing this method on Access 2003. I used to have Access 2000, but I can't recall the details of the interface, so it is possible my suggestion will not apply, but I think they were about the same as far as the menus went.
Allen's other suggestions apply to Access 2000 as well as 2003.

"majordud" <majordud@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2FC84D82-1B83-4696-AF8F-265F783BDEC3@xxxxxxxxxxxxxxxx
When I drop down the Tools/Macro menu in my Access 2000, I have options of
only Visual Basic Editor, or Run Macro - if I drop down the Tools/Security
menu, I have options of Set Database Password, User and Group Permissions or
Accounts, User Level Security Wizard, or Encrypt/Decrypt Database - these do
not give me the ability to change a macro security level, and nowhere else
do I see the ability to change the macro security level to anything. But
even if I did have such an option, I can guarantee that I never changed it -
so why is there the difference between the databases? What have I done wrong
(if I did)? and how do I fix it? I just created a new test db & the buttons
from the wizard work just fine - they won't in my previous db, and they do in
the db previous to that. What have I changed?
--
signed, me, myself and I.


"BruceM" wrote:

The suggestion for Access 2003 should work for Access 2000.

"majordud" <majordud@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:84A79365-D939-4587-ABBC-7ECF24F0B2E5@xxxxxxxxxxxxxxxx
> Thanks for your reponse, but as stated, I am using Access 2000 - > perhaps
> you
> could tailor your comments more specifically for 2000?
> -- > signed, me, myself and I.
>
>
> "Allen Browne" wrote:
>
>> Perhaps it is a security setting.
>> In Access 2003, go to Tools | Macro | Security, and set the Macro
>> security
>> to Low.
>> In Access 2007, make sure the database is in a trusted location via:
>> Office Button | Access Options | Trust Center | Trust Center >> Settings
>>
>> Alternatively, there could be a problem with library references in the >> db
>> where it doesn't work. For solving problems with references, see:
>> http://allenbrowne.com/ser-38.html
>>
>> To help track down what's wrong, you need to be able to see your error
>> messages. In the code window, go to:
>> Tools | Options | General
>> and set Error Trapping to "Break on Unhandled Errors."
>> In the options of the main Access window, make sure you have not >> disabled
>> Special Keys in the startup.
>>
>> -- >> Allen Browne - Microsoft MVP. Perth, Western Australia
>> Tips for Access users - http://allenbrowne.com/tips.html
>> Reply to group, rather than allenbrowne at mvps dot org.
>>
>> "majordud" <majordud@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:F201863B-3B8A-48EC-9692-CFF98B9940CE@xxxxxxxxxxxxxxxx
>> > Using Access 2000, I have built an extensive database, & the command
>> > buttons
>> > built with the Wizard all work. All simple commands, such as Print,
>> > Find
>> > Record, etc. I build another database (ostensibly with all the same
>> > settings) and the command buttons built with the Wizard will not >> > work -
>> > none
>> > of them - when clicking on such a button, it depresses, but nothing
>> > happens.
>> > I build another database, and the command buttons built with the >> > Wizard
>> > all
>> > work. Why? What variable is available that apparently switches off
>> > all
>> > the
>> > buttons? The macro code established by the Wizard in a db that >> > works
>> > is
>> > identical to the macro code in the db that doesn't work.
>> > Suggestions?
>> > -- >> > signed, me, myself and I.
>>
>>



.

Loading