Rocky Smolin at Beach Access Software
rockysmolin at bchacc.com
Sat Dec 22 15:28:03 CST 2007
Aha! DoEvents. That's what I need.
MT
Rocky
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Saturday, December 22, 2007 10:48 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Spell Check
Hi Rocky,
The button on the form "on click" sets the value to true If it is True,
then YOUR routine picks this up an exits.
That is why the doevents is there.
Hth
Max
Ps. Sorry if this is garbled, Rocky, but I am really drunk and signing
off....
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Saturday, December 22, 2007 2:59 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Spell Check
Max:
Is there something in the click event of the cancel button then?
Rocky
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Saturday, December 22, 2007 5:20 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Spell Check
Rocky,
What I do in situation like this is to have a button on the form with
"Cancel" on it (appears when the spell check is invoked).
In the Routine I have code something like this.
Dim bCancel as boolean
bCancel = Forms!myform!myCancelButton
Do while
...your code
bCancel = Forms!myform!myCancelButton
If bcancel = true then exit do
Doevents
Loop
Max
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Saturday, December 22, 2007 7:13 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Spell Check
Kevin:
That might do it. Not the 'perfect' solution for this client. But gets him
closer fur sure.
Originally there was just the one line: DoCmd.RunCommand acCmdSpelling.
Which meant he could hit Cancel and the spell check would stop.
But it checked all the fields which meant a lot clicking of 'Ignore All'.
He only wants to check the one field - TimeEntryNarrative - so I set him up
with that. But there's no way to stop the spell check once it starts and if
the underlying recordset isn't well filtered, then it takes a long time to
finish.
Thanks,
Rocky
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kevin Waddle
Sent: Friday, December 21, 2007 10:12 PM
To: 'Access Developers discussion and problem solving'
Cc: 'Rocky Smolin at Beach Access Software'
Subject: Re: [AccessD] Spell Check
Rocky,
Comment out the line...
'DoCmd.GoToRecord , , acFirst
And it will start from the current record.
By the way, nice code!
HTH,
Kevin
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Friday, December 21, 2007 7:54 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Spell Check
Dear List:
I have a spell check in an app built-in to a command button - spell checks
one text field on a continuous bound form. It works well, except that there
doesn't seem to be a way to interrupt it once it's started. I tried a few
different events thinking I could set a tag in a control, and, in the spell
checking loop, look for a change in the tag. But nothing seems to trigger
while it's in the loop.
I've modified the routine to spell check only the current record. But it
would be nice to be able to spell check forward from the current record to
the end of the recordset but give the user a way to escape if the
accidentally start the spell check and want to abort it. Spell checking the
whole recordset at the moment takes about 10 minutes.
Any ideas?
Here's the code. It's pretty simple:
DoCmd.GoToRecord , , acFirst
Do While Me.NewRecord = False
Me.TimeEntryNarrative.SetFocus
Me.TimeEntryNarrative.SelStart = 0
If Not IsNull(Me.TimeEntryNarrative) Then
Me.TimeEntryNarrative.SelLength = Len(Me.TimeEntryNarrative)
DoCmd.SetWarnings False
DoCmd.RunCommand acCmdSpelling
DoCmd.SetWarnings True
End If
DoCmd.GoToRecord , , acNext
Loop
MTIA,
Rocky
.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.5/1191 - Release Date: 12/20/2007
2:14 PM
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.5/1191 - Release Date: 12/20/2007
2:14 PM
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.5/1191 - Release Date: 12/20/2007
2:14 PM