Jim

>Actually, I think using a form method is a better design. That way you can >have a formbutton, a toolbar button, a key, and a menu option that all call the >same code

I'm going the menu route (see my last post to Erik Moore) - as this will available to all forms throughout the app and requires the minimum additional coding. As Erik points out, the menu shortcuts don't suffer the interprocessing problem. And as they can be defined with all the hotkey combinations I currently use - and can be enabled/disabled by 'skipping' for various conditions, the menu answer now seems the most obvious alternative to a large number of OKLs...

Thanks

Harry