Spelling 101

[Nick 'The Database Guy']

Hi,

I am fully aware of the F7 spell check in access, and I am also aware
that this can be automated with the statement,

SendKeys "{F7}"

However when you do this you are presented with a message box that
tells you that the spell check is complete, even if the spell check has

made no corrections.

My question is: Is there any way of doing a spell check invisibly? I
realise that this might involve using the windows API.

Thanks In Advance

Nick

[salad]

Nick 'The Database Guy' wrote:

Hi,

I am fully aware of the F7 spell check in access, and I am also aware
that this can be automated with the statement,

SendKeys "{F7}"

However when you do this you are presented with a message box that
tells you that the spell check is complete, even if the spell check has

made no corrections.

My question is: Is there any way of doing a spell check invisibly? I
realise that this might involve using the windows API.

Thanks In Advance

Nick

Why would you want to spell check invisibly? What would be the purpose?
What if you wanted to keep a word the spell check can't find? What if
there were several options to select from if you did want to change it?

[deluxeinformation]

salad wrote:

Nick 'The Database Guy' wrote:

Hi,

I am fully aware of the F7 spell check in access, and I am also aware
that this can be automated with the statement,

SendKeys "{F7}"

However when you do this you are presented with a message box that
tells you that the spell check is complete, even if the spell check has

made no corrections.

My question is: Is there any way of doing a spell check invisibly? I
realise that this might involve using the windows API.

Thanks In Advance

Nick

Why would you want to spell check invisibly? What would be the purpose?
What if you wanted to keep a word the spell check can't find? What if
there were several options to select from if you did want to change it?

Perhaps he doesn't want a 'spell check complete' message if there are
in fact no errors.

Bruce

[salad]

de***************@gmail.com wrote:

salad wrote:

>>Nick 'The Database Guy' wrote:

>>>Hi,

I am fully aware of the F7 spell check in access, and I am also aware
that this can be automated with the statement,

SendKeys "{F7}"

However when you do this you are presented with a message box that
tells you that the spell check is complete, even if the spell check has

made no corrections.

My question is: Is there any way of doing a spell check invisibly? I
realise that this might involve using the windows API.

Thanks In Advance

Nick

Why would you want to spell check invisibly? What would be the purpose?
What if you wanted to keep a word the spell check can't find? What if
there were several options to select from if you did want to change it?

Perhaps he doesn't want a 'spell check complete' message if there are
in fact no errors.

Bruce

That may be true. He could send
SendKeys "{F7}"
SendKeys "{Enter}"
But what if there were a word that was spelled wrong. Then it would
select it and he'd still get the message.

I would prefer knowing the spell check was complete if I initiated it.

[Lyle Fairfield]

"Nick 'The Database Guy'" <ni*****@btinternet.comwrote in
news:11**********************@l12g2000cwl.googlegr oups.com:

I am fully aware of the F7 spell check in access, and I am also aware
that this can be automated with the statement,

SendKeys "{F7}"

Some developers consider SendKeys to be dangerous in that the send might
end up in some other currently running application or some other Access
window. I've never seen this happen and doubt that it's more than a bourbon
myth but I avoid SendKeys because IMO SendKeys is an ugly hack created for
the rescue of the lazy, the incompetent and the indifferent.

You might try

With DoCmd
.SetWarnings False
.RunCommand acCmdSpelling
End With

The help file says:
"If you turn the display of system messages off in Visual Basic, you must
turn it back on, or it will remain off, even if the user presses CTRL+BREAK
or Visual Basic encounters a breakpoint."

If the help file is correct (a 50-50 possibility) then somewhere, sometime
one should do:

DoCmd.SetWarnings True

I wouldn't know as I never mess with SetWarnings. If I had a gnarly text
box or memo where spelling is a problem I would be inclined to have a
nearby label with the caption:
"<F7to check spelling."
When one respects users and places the responsibility for proper data entry
on their shoulders one is usually rewarded with good data entry.

A good Access application is marked by its simplicity. Magic buttons are
great for laughs and termination justification.

[Larry Linson]

"Lyle Fairfield" <ly***********@aim.comwrote

If the help file is correct (a 50-50 possibility) then
somewhere, sometime ...

Ever the optimist, aren't you, Lyle? :-)

[Nick 'The Database Guy']

I feel that Lyle's comment: "When one respects users and places the
responsibility for proper data entry on their shoulders one is usually
rewarded with good data entry." was equally optimistic. As this
request for information came from a user request. Also the database
that I was called in to sort out had a great number of spelling
mistakes.

Even users have deadlines I guess.

Nick

Larry Linson wrote:

"Lyle Fairfield" <ly***********@aim.comwrote

If the help file is correct (a 50-50 possibility) then
somewhere, sometime ...

Ever the optimist, aren't you, Lyle? :-)

[Nick 'The Database Guy']

As a matter of interest I used the following code:

Public Function Spell()
' Arvin Meyer 9/17/1998
' Adapted from code by Terry Wickenden
Dim ctlSpell As Control
Dim frm As Form
Set frm = Screen.ActiveForm
DoCmd.SetWarnings False
' Enumerate Controls collection.
For Each ctlSpell In frm.Controls
If TypeOf ctlSpell Is TextBox Then
If Len(ctlSpell) 0 Then
With ctlSpell
.SetFocus
.SelStart = 0
.SelLength = Len(ctlSpell)
End With
DoCmd.RunCommand acCmdSpelling
End If
End If
Next
DoCmd.SetWarnings True
End Function

This was posted by Arvin Meyer and my thanks go out to him and
everybody else that gave me feedback.

Nick
Nick 'The Database Guy' wrote:

I feel that Lyle's comment: "When one respects users and places the
responsibility for proper data entry on their shoulders one is usually
rewarded with good data entry." was equally optimistic. As this
request for information came from a user request. Also the database
that I was called in to sort out had a great number of spelling
mistakes.

Even users have deadlines I guess.

Nick

Larry Linson wrote:

"Lyle Fairfield" <ly***********@aim.comwrote

If the help file is correct (a 50-50 possibility) then
somewhere, sometime ...

Ever the optimist, aren't you, Lyle? :-)

[Lyle Fairfield]

Nick 'The Database Guy' wrote:

I feel that Lyle's comment: "When one respects users and places the
responsibility for proper data entry on their shoulders one is usually
rewarded with good data entry." was equally optimistic. As this
request for information came from a user request. Also the database
that I was called in to sort out had a great number of spelling
mistakes.

Even users have deadlines I guess.

!