Main Switchboard won't activate sub-switchboard

[Guest]

Can someone help me work out why not? I have put quite some time into
understanding the entries in the "Switchboard items" table by comparing with
a sample database. All the entries appear to be correct, but the go to
switchboard button in the main default switchboard (1) just will not activate
the sub-switchboard (2). The switchboards were both set up using the
Switchboard manager.

I'm running Access 2000 under XP.
Cheers K.

 

[Guest]

Suggest that you post the contents of your Switchboard Items table. This will
assist others in long distance troubleshooting.

You might want to look into creating your own switchboard using an unbound
(ie. no recordsource) form. Use the command button wizard to create buttons
to open your desired forms and reports. It's really quite simple, and much
less problematic versus the switchboard wizard build switchboards.

Tom
__________________________________________

:

Can someone help me work out why not? I have put quite some time into
understanding the entries in the "Switchboard items" table by comparing with
a sample database. All the entries appear to be correct, but the go to
switchboard button in the main default switchboard (1) just will not activate
the sub-switchboard (2). The switchboards were both set up using the
Switchboard manager.

I'm running Access 2000 under XP.
Cheers K.

 

[Guest]

Thanks for your interest Tom. Somehow I don't think the switchboard items
tyable contents are going to help, but here they are.

I deleted the original more cpomplex one that didnt work, and created a much
simplified one to try to at least get something very basic to kick off, and
work from there. Unfortunately even this basic one won't work.

I hope the tabulation below holds.

SwitchboardID ItemNumber ItemText Command
Argument
1 0 Main Menu
0 Default
1 1 Reports Menu
1 2
1 2 Exit Database
6 (blank)
2 0 Reports Menu
0 (blank)
2 1 Run Bonus Statements
4 RptBonus
2 2 Return to Main Menu
1 1
Thanks Tom.
Regards K.

 

[Guest]

I was able to get a switchboard to work correctly, using the entries that you
supplied in the Switchboard Items table, with a new Switchboard form that I
had the wizard create. I added a report to the sample database named
"RptBonus". Everything seems to be working fine on my end.

I invite you to send me a compacted & zipped copy of your database. I can
test it and see if it works on my PC. Have you tried this database on another
PC, just to rule out any problems related to the PC itself?

Just in case your switchboard form is corrupted, you can delete the form.
Rename your existing Switchboard Items table to some other name (Switchboard
ItemsX). Then start the wizard, so that it will create a new form. Close the
wizard without spending any time adding items. Then delete the brand new
Switchboard Items table. Finally, rename Switchboard ItemsX back to
Switchboard Items. In case your problem was caused by some type of corruption
in the code behind the Switchboard form, this process of having the wizard
create a brand new form should fix it.

Tom

QWaos168@XScom cast. Dnet (<--Remove all capitolized letters and spaces).

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

Thanks for your interest Tom. Somehow I don't think the switchboard items
table contents are going to help, but here they are.

I deleted the original more complex one that didnt work, and created a much
simplified one to try to at least get something very basic to kick off, and
work from there. Unfortunately even this basic one won't work.

I hope the tabulation below holds.

SwitchboardID ItemNumber ItemText Command
Argument
1 0 Main Menu
0 Default
1 1 Reports Menu
1 2
1 2 Exit Database
6 (blank)
2 0 Reports Menu
0 (blank)
2 1 Run Bonus Statements
4 RptBonus
2 2 Return to Main Menu
1 1
Thanks Tom.
Regards K.

__________________________________________

:

Suggest that you post the contents of your Switchboard Items table. This will
assist others in long distance troubleshooting.

You might want to look into creating your own switchboard using an unbound
(ie. no recordsource) form. Use the command button wizard to create buttons
to open your desired forms and reports. It's really quite simple, and much
less problematic versus the switchboard wizard build switchboards.

Tom
__________________________________________

:

Can someone help me work out why not? I have put quite some time into
understanding the entries in the "Switchboard items" table by comparing with
a sample database. All the entries appear to be correct, but the go to
switchboard button in the main default switchboard (1) just will not activate
the sub-switchboard (2). The switchboards were both set up using the
Switchboard manager.

I'm running Access 2000 under XP.
Cheers K.

 

[Guest]

Hi Tom,

Thanks again for your help on this. Form corruption indeed appears to have
been the case and I have successfully recreated a working version.

Although creation of a "switchboard" with the manager is so easy, our
suggestion re: creating a front-end menu using unbound forms appeals to me,
because of the ability to tailor sub-menus, and even more importantly the
possibility of running update queries from a menu. The switchboard doesn't
givbe you a way of doing that - unless there is an esoteric method! (I have
tried calling it from a form or report, but the dialogue boxes in the wizard
don't list update queries, only standard ones).

If you could post a step-by-step method, for us dummies as to how to create
the most simple front-end menu with, say just a main and one sub-menu each
with 2 items, that would enable many of us to "go from there"

Thanks again, Tom.
Kind regards,
K

 

[Guest]

Tell you what...if you send me an e-mail message, with a valid return
address, I will send you a Word document I have available that details how to
do this. The unbound switchboard does not have sub-menus, similar to the
Switchboard Manager build switchboards. You can use a tab control to separate
areas of functionality.

If my answer has helped you, please answer yes to the question that reads
"Did this post answer the question?" at the bottom of the message thread.


Tom

QWaos168@XScom cast. Dnet (<--Remove all capitolized letters and spaces).

http://www.access.qbuilt.com/html/expert_contributors.html
_______________________________

:

Hi Tom,

Thanks again for your help on this. Form corruption indeed appears to have
been the case and I have successfully recreated a working version.

Although creation of a "switchboard" with the manager is so easy, our
suggestion re: creating a front-end menu using unbound forms appeals to me,
because of the ability to tailor sub-menus, and even more importantly the
possibility of running update queries from a menu. The switchboard doesn't
givbe you a way of doing that - unless there is an esoteric method! (I have
tried calling it from a form or report, but the dialogue boxes in the wizard
don't list update queries, only standard ones).

If you could post a step-by-step method, for us dummies as to how to create
the most simple front-end menu with, say just a main and one sub-menu each
with 2 items, that would enable many of us to "go from there"

Thanks again, Tom.
Kind regards,
K

 

[Michael Cannizzaro]

Thanks for your interest Tom. Somehow I don't think the switchboard items
tyable contents are going to help, but here they are.

I deleted the original more cpomplex one that didnt work, and created a much
simplified one to try to at least get something very basic to kick off, and
work from there. Unfortunately even this basic one won't work.

I hope the tabulation below holds.

SwitchboardID ItemNumber ItemText Command
Argument
1 0 Main Menu
0 Default
1 1 Reports Menu
1 2
1 2 Exit Database
6 (blank)
2 0 Reports Menu
0 (blank)
2 1 Run Bonus Statements
4 RptBonus
2 2 Return to Main Menu
1 1
Thanks Tom.
Regards K.

Maybe there's a problem with one of the switchboards
If you can, you can buy one of each switch board, install them, and see if
that helps.
Bye!
Michael

 

[Guest]

Thanks Tom. Both emails are waiting now in my in-box.
You will be interested to kn0ow that I have inadvertently repeated the
action that corrupted my original switchboard: As a result of a post to this
board many months ago asking how to open my switchboard maximised by default,
I inserted the command, "=DoCmd.Maximize" on the "On open" line in the
switchboard's properties form. Obviously it doesn't like it - possibly
because it obliterates somnething else that was needed. There must be a way
to have a switchboard open maximised by default - after all its supposed to
be a front end, and who wants staff to be confronted with a cluttered screen
when the front end of a database solution opens?

Thanks for your help. I'm going to look at your database now. I'm
disappointed with the unbound form method though, if it is unable to cope
with nested menus. Mmm, a tab control... Yes, you mean like a page with a
tab, like the speadsheets in Excel or in dialogue boxes. That would probably
be as good as nested menus, even if a little unconventional from a front-end
point of view.

Will go and look at your database now, thanks.

Regards,
K.

 

[Guest]

Hi Kevin,

One way of opening your switchboard maximized is to use a macro specifically
named Autoexec:

Action = Openform

In the lower window, which you can toggle to by using F6, specify the name
of your switchboard form. Then add a second Action = Maximize.


Tom
_______________________________________

:

Thanks Tom. Both emails are waiting now in my in-box.
You will be interested to kn0ow that I have inadvertently repeated the
action that corrupted my original switchboard: As a result of a post to this
board many months ago asking how to open my switchboard maximised by default,
I inserted the command, "=DoCmd.Maximize" on the "On open" line in the
switchboard's properties form. Obviously it doesn't like it - possibly
because it obliterates somnething else that was needed. There must be a way
to have a switchboard open maximised by default - after all its supposed to
be a front end, and who wants staff to be confronted with a cluttered screen
when the front end of a database solution opens?

Thanks for your help. I'm going to look at your database now. I'm
disappointed with the unbound form method though, if it is unable to cope
with nested menus. Mmm, a tab control... Yes, you mean like a page with a
tab, like the speadsheets in Excel or in dialogue boxes. That would probably
be as good as nested menus, even if a little unconventional from a front-end
point of view.

Will go and look at your database now, thanks.

Regards,
K.

 

[Guest]

Thanks Tom, I'll do that. Haven't had the time yet to explore the tab-form
method, but will be interested to do that shortly.
Regards,
K