>This would be seriously bad news!
>
>I have defined no less than 104 hotkeys into my application and my users would Lynch me if they even read the above! Keyboard actions are up to 1000% more efficient with skilled users doing bulk data input and there is no way in the world they (or I) could accept the loss of the hot keys. We'd have no option but to stay in dos if it was that serious.
>

I didn't even know there were 104 possible combinations... :-)


>However, we've been using bits of the vfp version on a standalone basis in trials and training, and, so far, thats one of the areas where we don't have a problem. All the hot keys are doing their jobs with remarkably little fuss. However, whether we'll survive the transition to multi-user so easily is a horse of a different feather! So y' got me worried dude!
>

I don't think that Multi-user will throw anything into the OKL mix. If you are having good luck so far with OKLs, then by all means stick with 'em. Just keep in mind the possibility of future funkiness.

>So - is there any call -even a low level call to the system - that can tell us when form processing has ended and it is safe to proceed? If so I can insert such a call at the critical part of the hot key code...
>

Not that I know of, but you can manage it yourself by having your ime intensive processes set a busy flag at the beginning and unset it when they are finished, and then have your OKL routines check for the flag before continuing.



>Or can you create an invisible but active form just full of "hotkey buttons" appropriately defined which could part of each relevant formset...
>

I'm afraid this won't work- hot key buttons only work when the form is active.