It is entirely possible that you're confusing the issue between dialog
forms, and what are known as model forms in MS access.
Dialog forms do not allow the cursor/focus to use any of the custom or built
in menus at all. The behavior is the same as if in code you displayed a
msgbox command. Now how when using a msgbox command you can not use menus,
or have the focus move to anything other than that actual form (or dialog
box). This includes also the built in menus, or in your case custom menu
bars, they simply cannot be used in any way shape or form when you use a
dialog form. (or the msgbox command...you can even try this from the debug
window, and type in:
msgbox "hello"
now, try and use the menus...you can not untill you hit ok.
It appears that my menus work fine in forms that are not modal dialog
windows
modal disalog form??? Model forms, and dialog forms are VERY VERY much
different animals.
I have a few forms that are opened modally AND non-modally depending on
the
calling form. Modal = no workie.
The above information is likely incorrect, since the openform command has NO
way of setting a form as modal, or non model via the open command. You can
certainly supply the acdialog parameter, and the form will open as dialog,
but that is NOT the forms model setting, and is very much a differnt setting
alltogher.
If you want to open a form as model in code, then you have to go:
dim strF as string
strF = "name of my form goes here"
docmd.OpenForm strF
forms(strF).modal = true
>
Is this a known limitation? Is there some sort of setting somwhere or VBA
code I can write to work around this?
Keep in mind the difference between modal, and dialog forms, I explain the
difference here:
http://www.members.shaw.ca/AlbertKal...log/Index.html
are you use you need dialog forms, or will a modal form suffice?
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com