SpellCheck losing data

  • Thread starter Thread starter FPS, Romney
  • Start date Start date
F

FPS, Romney

Don't know if anyone else has run into this problem, but periodically when
using Spell Check -- via either the tool bar icon or the F7 key -- in
fields being edited on a new, unsaved record, upon closing Spell Check the
fields on that record are blank. I *think* that this problem is most likely
to occur when the Ignore button has been used for one or more words in the
fields. Sometimes, going off the record (to another record) and returning
results in the data showing up again; sometimes not -- the data is simply
lost. Likewise using the Esc key -- sometimes this helps, sometimes not.

I've noticed this occur on both networked and non-networked databases and on
Access2000/2002 (WinXP), as well as Access97 (Win98).

I imagine the fact that it is a new record that is being edited has a lot to
do with it. I'm wondering if anyone else has run into this problem. Should
I insert a SaveRecord command somewhere between opening and closing Spell
Check? Which event(s) would be the most appropriate -- OnLostFocus?

Thanks for any help.
Mark
 
Nope, ONLOSTFOCUS doesn't work -- opening Spell Check with either method
evidently doesn't automatically change the focus -- *unless* the Change
button on Spell Check has been clicked. Then the focus must change because
the record is saved prior to closing Spell Check.
Mark
 
I found one reference to this same problem through a Google search (Ken
Snell 8/20/03 ). If I read his response right, It seems that there's not an
easily accessible event triggered by opening Spell Check. I guess I could
remove the Spell Check icon from the toolbar and capture the F7 keypress
event for each control, followed by a SaveRecord command. Or, I could
simply place a warning on the form advising the user to save the record
before using Spell Check. (The first idea is probably better).

If anyone else has any other ideas or suggestions for this, I would sure
appreciate them.
Thanks,
Mark
 
In case anyone reads this thread, the following seems to work:
-- removed the Spell Check icon from the toolbar
-- placed the following code for the keydown event on any field where Spell
Check would likely be used. (A note on the "BaselineData" form mentions
using F7 for Spell Check).

Private Sub BaselineData_KeyDown(KeyCode As Integer, _
Shift As Integer)
If KeyCode = vbKeyF7 Then
DoCmd.RunCommand acCmdSaveRecord
End If
End Sub

Mark.
 
Back
Top