Right after the line of code above do:
WriteLn(@Error)

If it says Yes, then it can't find the item you are trying to hide. If this is the case, check your spelling and names.

If you want to prevent a Form called Employee from being opened in Search from the application menu, you probably just want:
vHideTree = @HideTreeItem("Employee Database!Forms!Search/Update!Employee!Employee")

TreeItem paths don't continue off into other menus or into dialog boxes. They are not commands. They cannot reference anything other than a findable path to a single item on a single menu tree.

Quote:


@Error returns runtime errors, not a syntax errors. The "test program" can only chack for syntax errors. You need to run the program to check for @error conditions.

Hello Louis,

You have to call @Error immediatly after the first @HideTreeItem to see if it is failing.

So your code would be

var vHideTree as Int

vHideTree = @HideTreeItem("Employee Database!Forms!Search/Update!Employee!Employee!Search Menu")

WriteLn(@error)

This would tell you if there is a problem with this HideTreeItem.

The code you want is simply

vHideTree = @HideTreeItem("Search Menu") 

-Ray

Well, I tried both of the codes below with the @error function and it still indicates NO and does not hide the Search menu, so I am stumped.

Out of curiosity, why can you shorten the path to the Search menu that much ?  I assumed that you had to indicate every level for the function to work properly.

Louis

Hello Louis,

Put the vHideTree = @HideTreeItem("Search Menu") call in your forms on retrieve spec open programming.

Quote:


You do have to indicate every level for the tree that you are on, but the Search Menu is not part of the Application menu. There are essentially four different trees. The Application Menu, Search Menu, Add Data Menu, and Search Update Menu.

-Ray

Ray's previous suggestion to put the code into the On Retrieve Spec Open hides the Search menu but leaves the command area still there, but blank.  I was really trying to close this Command Area automatically when a user goes into the Search/Update mode (or add data mode) so that the whole form could be seen.

I tried Mark's suggestion with CloseCommandArea but that closes the Application menu as well. 

It sounds like I have to do a custom menu to deal with this unless there is another way to Close the command areas other than on the Application menu.

Thanks for the help.

Louis

Thanks for following thru on this.  This is what I have done:

App Property Manager - On App open: CloseCommand Area state is open

In the Employee Form - On Form Entry: CloseCommand Area state is closed

In the Employee Form - On Form Change: CloseCommand Area state is closed

In the Employee Form - On Retrive Spec Open: CloseCommand Area state is closed

In the Employee Form - On Form Exit: 2 CloseCommand Area states: open first then closed

The effect is that the application menu should always appear but when you go into search update, the search menu is hidden when you scroll thru records or change data and when you exit back out to the App Menu, the App Menu is still visible.

One problem still:  when you exit add data, it hides the App Menu and I am not sure how to fix this.

Would an Event called On Add or Exit Data Menu / On Add or Exit Seach Menu be useful ?

Thanks,

Louis