A 2010 Switchboard

[Dick7Access]

Can someone tell me what the difference is between making a form and adding CmdButtons to it and using switchboard manager and adding CmdButtons to it.
Thanks

 

[gemma-the-husky]

The MS switchboard is hierarchical

you set up options in a table

the switchboard displays a page of options, some options can open forms or reports, but other options can lead to another page of options, and the switchboard handles this automatically. You can add any number of options just by adding items to the underlying table.

If you have separate navigation forms, you have to keep editing the application to add new functions, or change the menu system.

also, if you are used to an accounts office type menu, in a big system - it can be the sort of menu that users expect to see.

I like the switchboard, and often use it.

 

[missinglinq]

Most experienced developers shun the Switchboard Manager. It offers a very limited number of options and is difficult to modify because of the cryptic way it handles things! IMHO, you're much better off using a standard Form and the Command Button Wizard to create your own switchboard..

Linq ;0)>

 

[gemma-the-husky]

Most experienced developers shun the Switchboard Manager. It offers a very limited number of options and is difficult to modify because of the cryptic way it handles things! IMHO, you're much better off using a standard Form and the Command Button Wizard to create your own switchboard..

Linq ;0)>

Without wishing to cause any disputations, I really disagree about the switchboard manager.

What does it not do, that you would want it to do?

 

[Dick7Access]

I have been making my own switchboard (sort to speak) for a long time, but I have seen some post come across about switchboard and started looking into it and at first glance, at least, I didn't see much difference. There’s a section in the cookbook, Dave, I will study it some more. Thanks all.
.

 

[stopher]

Here's why I don't use sbm. My comments are based on a limited, perhaps naive knowledge of sbm. Feel free to correct me.

The sbm is by default limited to 8 buttons. It's possible to go beyond this with some know how, but then you're rather negating any benefit of the sbm. Google this problem and most solutions will suggest build your own rather than trying to walk on water.

The sbm is limited in structure. Each button has to be the same (size, vertical position). I can't, for instance, have two columns of buttons afaik. All the labels have to be the same font.

Due to the enforced structure I cannot create custom buttons e.g. a button used in combination with a date selector

I can't make some buttons invisible e.g. based on the user's security

Every switchboard has to follow the same layout. Any style change on one will affect all others. So I can't have my customer switchboard as a different design to my product switchboard e.g. graphics for specifc switchboards.

I cannot create a button to directly open a form in datasheet view (sbm is set to single). I can get round this be writing an intermediary function. But the point is, why bother when this is a trivial exercise if I'd rolled my own.

Interestingly the Northwind Traders sample database does not use sbm. The main switchboard in Northwind is a good example why.

Personally I think the structure imposed by sbm is of the 80's. Interface design has evolved since then.

Chris

 

[bladedfeather]

i created a form to become my switchboard. i add a command button to open my employee form so the user can add another employee. when i click the command button i saw that all the records in the employee form was visible. how can i hide all the records and a blank record will see if i will open the form. hope somebody can help..thanks..

 

[missinglinq]

...how can i hide all the records and a blank record will see if i will open the form

If you always want the Form to open in this way, regardless of where/how you open it, in Form Design View, with the Form itself selected, go to
Properties - Data and set the Data Entry Property to Yes.

If you only want the Form to open in this manner when it is opened from the original Form, but open with all Records showing, when you open the Form independently, use this code behind the Command Button to open the Form:

DoCmd.OpenForm "YourTable", , , , acFormAdd

Linq ;0)>

 

[gemma-the-husky]

Here's why I don't use sbm. My comments are based on a limited, perhaps naive knowledge of sbm. Feel free to correct me.

The sbm is by default limited to 8 buttons. It's possible to go beyond this with some know how, but then you're rather negating any benefit of the sbm. Google this problem and most solutions will suggest build your own rather than trying to walk on water.

The sbm is limited in structure. Each button has to be the same (size, vertical position). I can't, for instance, have two columns of buttons afaik. All the labels have to be the same font.

Due to the enforced structure I cannot create custom buttons e.g. a button used in combination with a date selector

I can't make some buttons invisible e.g. based on the user's security

Every switchboard has to follow the same layout. Any style change on one will affect all others. So I can't have my customer switchboard as a different design to my product switchboard e.g. graphics for specifc switchboards.

I cannot create a button to directly open a form in datasheet view (sbm is set to single). I can get round this be writing an intermediary function. But the point is, why bother when this is a trivial exercise if I'd rolled my own.

Interestingly the Northwind Traders sample database does not use sbm. The main switchboard in Northwind is a good example why.

Personally I think the structure imposed by sbm is of the 80's. Interface design has evolved since then.

Chris

Chris,

I know this is a bit late for a response.

I have redesigned my sb to have 21 options - 2 columns of 10, and an extra "return" option. Relatively trivial exercise.

Personally I do not see a problem having multiple menus of a similar design - that's standard, isn't it - the access ribbons/menus are standard aren't they?

I think a consistent, repeatable menu is an adavantage, not a disadvantage.