Sheesh Martin - wherever did you dig up that link? Must’ve been written by Frank Soltis when they first had him go and speak there.
Great Stuff!

Anyway - back to the question - If you want a real menu. you’ll need to write it in UIM, which is a slightly idiosyncratic tag language. Many applications provide their own, often even more idiosyncratic menus.

If you really mean ‘how do I arrange that a user gets a menu when they sign on, then investigate their User profile
WRKUSRPRF command, and simply name the menu they get. You can also specify that they can *only* use menus and have no access to commands - thus they don’t damage your system. Don’t want users having access to anywhere they’re not wanted.

Hi,

I know it’s a really old link, but I think it’s nicely explained for newbies. Can’t remember how I came across it. I should probably store a copy somewhere in case it gets taken offline….

Cheers,

Martin.

Keeping it - good idea - Its good stuff. THere’s not all that much of the basics have altered, it’s just become much richer.

. . . everything is an object . . single level storage . . . objects are type checked . . . objects (may) have their own language . .

Yep - great stuff.
Cheap to own, doesn’t fall over. leaves a log and messages.

x86 and winxxx - eat yer heart out.

You can check out www.foursquares.ca. There is a custom menu system that is file driven, has user security. You can request a trial and see if it works for you. Best of all there’s no programming required.

I am not affiliated with them in any way, but we have used their menu system for years. It works very well and the person that writes it is very responsive to tech support and has added features for us if he thought they would be valuable to others.

http://www.handhtech.com/hhTech/extendMenu.htm