Thanks,
Carl Rapson
/xm is 123 Release 1's equivalent to either {menubranch MENU} or {menucall
MENU} in later versions, I don't remember which. This will be nasty.
Theoretically, the best way to translate this would be using a custon
toolbar resembling a menu. Next best would be the way later versions of 123
deal with these commands: putting them into a list box in a dialog.
Unfortunately, UI programming is something I've avoided, so I'm no help with
this. I understand roughly how this needs to be done. 123 custon classic
menus such are defined by ranges having one column per menu entry. In each
column, the top row is the text that will appear in the menu, the 2nd row is
the menu prompt - text that appears below the menu when the given item is
selected, and the subsequent rows are the macro statements run if the user
selects that menu item. If /xm == {menucall .}, then you could bundle each
of the macro statements in each column into separate Excel/VBA macros,
display either a custom toolbar/menu or listbox in a user form (dialog), and
use a Select statement based on the menu results to choose the macro to run.
I'm crossposting this on purpose to microsoft.public.excel.programming
because the people there are more likely to be of help than me when it comes
to Excel/VBA UI programming.
Carl Rapson
"Harlan Grove" <hrl...@aol.com> wrote in message
news:Od3kAg$WDHA...@TK2MSFTNGP12.phx.gbl...