Andrew,

You said that you did it previously, but did you make this form type "modal" ?

Check your email.

Bill


>Hi Bill,
>
>I think I'm doing what you suggested, and I'm getting essentially the same result as before.
>
>In sysmult.prg p0hotkeys procedure I added a call to my custom form
>
>

on key label f6 do form ajmenu

>
>and when I press my assigned hotkey the form comes up. However, it behaves just like the other one, it is visible, I can close it using the X in the top right corner, but no amount of clickin' on the form itself yields any joy..
>
>Any ideas what I am missing here?
>
>Thanks,
>
>
>Andrew
>>Andrew,
>>
>>In the config.fpw you will see two lines:
>>_GENMENU=".\GENMENUX.PRG"
>>_GENMENUX="GENMENU.PRG"
>>
>>If you create a shortcut to VFP that will have the vp10 directory as the statup directory or manually use that config.fpw with a "-c" on the command line then when you add/edit menu items and regen, it will work correctly.
>>
>>I have an alternate suggestion based on over 15 years of making mods to SBT. If you make a ton of mods to the software, then upgrades or even updates become a big deal and cost the client more money for you to reprogram the mods. After a while, they either won't want to make any more mods or will never want to upgrade because of the cost. In pro Series you can add menu items to the"custom" menu right in the system. For Visionpoint, I assigned a hotkey to call a custom form that would then present the user with all custom menu options including reports. There is a procedure in the sysmult procedure file called "p0hotkey" You can do your hotkey assignment there and if they get any updates, you only have two lines of code to change. I use a form based on an old idea from codebook where the menu is driven from a table so when you add new menu items, you just add it to the table and don't have to even edit the form.
>>
>>hope this helps,
>>Bill
>>
>>
>>
>>
>>>Hi Bill,
>>>
>>>VisionPoint 10.
>>>
>>>Thanks
>>>
>>>>Andrew,
>>>>
>>>>SBT didn't hand-code the menu's, they used a custom version of Genmenux. If you look in the config.fpw, you should see reference to the _genmenu variable. What version of SBT are you refering to and is it Visionpoint or Pro series?
>>>>
>>>>Bill
>>>>
>>>>>Hi Sergey,
>>>>>
>>>>>The problem for me is that I haven't done much coding of menus, always using the Menu Builder and resultant code. In this case, it looks mostly hand-coded, and it is very dense (many if-endifs, cases, etc.) so I am having difficulty seeing where the central READ EVENTS command takes place.
>>>>>
>>>>>My current VFP projects all rely on the READ EVENTS command, and my forms all automatically work under this scenario. Was there another way this was done in the past (which I never learned)?
>>>>>
>>>>>There is a command
>>>>>
>>>>> ACTIVATE MENU _MSYSMENU PAD programs
>>>>>
>>>>>
>>>>>I'm having a strange night now, as even the Windows XP search facility won't find files with the content that I KNOW is there, so I am unable to find any READ EVENTS anywhere in the code even if it exists. Do you know if there is any way other than READ EVENTS to process a menu? I see ON SELECTION. Does it somehow override the accessibility of a form in the focus loop?
>>>>>
>>>>>I'm not sure any of this is helpful at all, but if you have any ideas I'd sure appreciate it!
>>>>>
>>>>>Thanks for taking a look!
>>>>>
>>>>>Andrew
>>>>>
>>>>>>Hi Andrew,
>>>>>>
>>>>>>Menu didn't change much since Fox 2.x days so I'm not sure what 'old Foxpro menu coding' means. Can you elaborate?
>>>>>>
>>>>>>>Can anybody tell me how to integrate VFP forms into the old Foxpro menu coding structure?
>>>>>>>
>>>>>>>I can "DO formxyz" OK, but it doesn't get focus, even if I make it's WINDOWTYPE=MODAL
>>>>>>>
>>>>>>>TIA
>>>>>>>
>>>>>>>Andrew