From: JamesJ on
I'm using the RunCommand|Spelling in a macro and invoke it from a shortcut
menu on a form.
How do I keep the speller from wanting to move to the next record?
I have the form's Cycle property to Current Record.

Thanks,
James
From: Dirk Goldgar on
"JamesJ" wrote in message news:%23fexrbNtKHA.928(a)TK2MSFTNGP04.phx.gbl...
> I'm using the RunCommand|Spelling in a macro and invoke it from a shortcut
> menu on a form.
> How do I keep the speller from wanting to move to the next record?
> I have the form's Cycle property to Current Record.

So you just want to check the current record? Have your macro first select
the record, then check the spelling:

RunCommand SelectRecord
RunCommand Spelling



--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)

From: JamesJ on
Worked great.

Thanks,
James

"Dirk Goldgar" <dg(a)NOdataSPAMgnostics.com.invalid> wrote in message
news:52A6448C-D7CE-4D58-B38D-02DD824EAFFD(a)microsoft.com...
> "JamesJ" wrote in message news:%23fexrbNtKHA.928(a)TK2MSFTNGP04.phx.gbl...
>> I'm using the RunCommand|Spelling in a macro and invoke it from a
>> shortcut menu on a form.
>> How do I keep the speller from wanting to move to the next record?
>> I have the form's Cycle property to Current Record.
>
> So you just want to check the current record? Have your macro first
> select the record, then check the spelling:
>
> RunCommand SelectRecord
> RunCommand Spelling
>
>
>
> --
> Dirk Goldgar, MS Access MVP
> Access tips: www.datagnostics.com/tips.html
>
> (please reply to the newsgroup)
>