Wrox Programmer Forums
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old January 7th, 2005, 10:52 AM
Friend of Wrox
Join Date: Mar 2004
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts

You can use an unbound form or forms, and the button wizard. That will do all the VBA for you. No more switchboards.

Old January 7th, 2005, 05:33 PM
Registered User
Join Date: Jan 2005
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts

Also, no ability to let non-Admins edit your menu options.

-- WillYum
Old January 7th, 2005, 06:01 PM
Friend of Wrox
Join Date: Oct 2004
Posts: 564
Thanks: 0
Thanked 4 Times in 4 Posts

True, but do you really want non-admin's messing with your menu(s)?

In my experience the less "monkeying around" access given to end users, the better.

Old April 2nd, 2007, 08:29 AM
Authorized User
Join Date: Dec 2006
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to FalseParadigm

quote:Originally posted by echovue
 In my experience the less "monkeying around" access given to end users, the better.
Agreed. Someway...somehow...when a user enters an database with free reign, something always gets hosed. I'll never say anything bad about the staff I work with, but their capacity to destroy is beyond my understanding.

That said, after a user accessed one of our databases, I began getting the same error that the OP is getting. Interestingly enough, there is no switchboard involved. Just a sub in a module that prints a report and closes the database. That's it.

Compiling does not reveal anything wrong, and I find nothing wrong with the code itself. The error occurs after the report prints and the database is getting ready to close.

Incidentally, if anyone knows what the error number is for this error, I want to try some special error handling for it as a temporary fix until I can take the time to rebuild the whole database (and pray it works).


"It's my way, or the Hemingway."

Similar Threads
Thread Thread Starter Forum Replies Last Post
Opening Switchboard with VBA rhysduk Access VBA 8 February 5th, 2014 12:31 AM
Switchboard Size ru1 Access 1 April 18th, 2006 11:31 AM
Switchboard ?s JeffGirard Access 1 September 15th, 2005 02:52 AM
Switchboard Manager penta Access 2 March 10th, 2005 06:43 AM
switchboard problems zisko3 Access 2 January 31st, 2004 03:52 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.