Re: Command Button Wizard

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.



.