Creating a Menu Bar

ghudson, thats actually a good idea that i have not tried. I can test it once i reach my home computer. I know when i was initially creating my menu bar i had many problems, and the MSaccess help file told me to recall the function on the form. But I hope you are right... That would save me alot of extra code if so.

I'll reply to this post once I get home so i can test.
 
Throw the function in a module and label it public.
Public functions in a module are available to all forms.

Jon
 
Great conversation!

In my program, the functions are in a module (Menu Module) and all are public.

As I mentioned before, they do come up sometimes without error but more often with the aforementioned error. I will try to identify what causes the change.

Treason, I surely hope you are wrong as several of these functions are global in nature. They will be much more efficient and easier maintained in a module.
 
can someone zip the Access 97 menu creator? I cant download it for some reason.

Thanks!
 
Why does anyone need a menu creator? You ismply goto view->toolbars->customize.

Create your menu / tool bar right from there...use the reports menu bar / toolbar property you can use this with forms too. Why put useless code in your apps?

Jon
 
Known Error Documdented by Microsoft

I found in the newsgroup comp.databases.ms-access a reference to MS Document Q193167 "ACC97: Error When You Click a Custom Command Bar Button" with the following information:

SYMPTOMS
When you click a menu or button on a command bar, you may see the following error message:

"The expression you entered has a field, control or property name that Microsoft Access can't find. "

CAUSE
This problem happens when the database has a long file name, and you assign a function using the following syntax:
.OnAction = "=<function name>()"
[My filename is HMS97_Rev16.mdb hardly long but outside of DOS!]

RESOLUTION
Do not include an equal sign (=) and parentheses (()) when you assign the function to the OnAction property of the command bar. For example, assign the OnAction property using the following syntax:

.OnAction = "<function name>"

STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 97.

The article is located at http://support.microsoft.com/default.aspx?scid=kb;en-us;193167

I am going to test their resolution.
 

Users who are viewing this thread

Back
Top Bottom