Autokeys macro - trapping ^c causing problems/irritations in design mode

[A C]

Hello

We have an AutoKey macro trapping ^c (copy), it runs some code when ^c is
detected.

We are having problems in design mode when trying to copy data from a
control's Properties dialog, for example trying to copy the row source sql
from a drop down box. We get the following Action Failed dialog:
Action Failed
Macro Name: AutoKeys.^c
Condition: True
ActionName: RunCode
Arguments: <our_routine_name()>

If we try and copy text or controls etc on the form in design mode it is
fine, no problems. It only causes problems (so far...) in the Properties
dialog box. Does anyone know what the problem here is?

We could of course turn autokeys off while we are developing etc but at this
stage we are interested in finding the cause and a fix it possible.

Thanks
AC

 

[Guest]

Try opening your database while holding down the shift key, to prevent the
Autokeys macro from running. Either this, or temporarily rename Autokeys to
something else. If your finished product will be delivered in .mde format,
then I think you could set up a conditional test to run Autokeys only if the
file type detected was .mde.

Tom
____________________________________________

:

Hello

We have an AutoKey macro trapping ^c (copy), it runs some code when ^c is
detected.

We are having problems in design mode when trying to copy data from a
control's Properties dialog, for example trying to copy the row source sql
from a drop down box. We get the following Action Failed dialog:
Action Failed
Macro Name: AutoKeys.^c
Condition: True
ActionName: RunCode
Arguments: <our_routine_name()>

If we try and copy text or controls etc on the form in design mode it is
fine, no problems. It only causes problems (so far...) in the Properties
dialog box. Does anyone know what the problem here is?

We could of course turn autokeys off while we are developing etc but at this
stage we are interested in finding the cause and a fix it possible.

Thanks
AC

 

[Steve Schapel]

AC,

I am not sure of the reason for the specific problem, as I have never
done anything quite like this myself. It could be, I suppose, that
whatever it is that your RunCode action does is not applicable in some
situations. But it is also not clear what you are trying to do here. I
would avoid using one of the commonly used built-in key combinations,
such as Ctrl+c, as part of an AutoKeys macro.