Thanx for the prompt reply. I am new to Accsess and do not quite understand. Is it possible to explain your concept to me as if to a 2 year old.Why not just create a form with subforms and use that instead of a switchboard. In your DB options you can set the form to be displayed on start up.
A switchboard is just a special case of a form so you can use a form instead. This means you can use a form instead which gives you extra flexibility. You just need to design what you wantThanx for the prompt reply. I am new to Accsess and do not quite understand. Is it possible to explain your concept to me as if to a 2 year old.![]()
Chris, when I say I am a begginer I mean just that. I have a a vauge idea of what you are talking about, but the application thereof eludes me.I agree with Rabbie. Create a blank form. Then add a buttons using the wizard. It will hold your hand through lots of custom design. If you do a button wrong then just delete it and add a new button.
Chris
I would DEFINITELY use the inbuilt switchboard manager
I agree with jashgtp. I suggested the same thing in #2 and #4. Jashgtp added clear instructions on how to do this.the OP is a beginner, that has not used access much.
I have only used access for a little while and just making a navigation page as per i descibed is pretty easy and think most people can get it to work
ive modified the standard switchboard manager to give slightly changed functionality, (more informative error messages, and validating the user against the menu items) and I have 17 buttons, not 8 - but you dont HAVE to make any changes
i also always edit the switchboard items table directly.
However, if you need a hierarchical multi-page menu - say you have 40 or 50 forms etc, then the inbuilt switchboard automatically deals with this - and this behaviour is quite tricky to achieve directly.
A single page form is fine though, if you can get all your functionality ON a single page.
I suspect the thing to do is to get a mechanism/design that works for you - then just clone it from database to database.
menu item description command argument
1 0 Main Menu Title
1 1 System form 3 frmsystem
1 2 Entry form 3 frmEntry
1 3 Different Menu 1 6
6 0 Sub Menu 6 Title
6 1 Amend Form 3 frmAmend
6 2 Delete form 3 frmDelete
6 8 Return 1 1
I too would opt for a form, create a FORM called Menu. Access 2007 (and back to Access 97), Access Options > Current Database > Display Form put Menu.
On the Menu put buttons and OnClick some action including calling other Menus.
To me the Menu system is just another Form. Here's an example:
http://www.designedlogic.com/ReportsExample04.html
Simon