Hi Tony,
Those are great suggestions!
As an aside, I use temp tables in that way many times, and I do have a bloat
problem with my main application, Instant Quote Pro. One thing I tried to
do, but I'm not even sure this helps, is to offload temp tables such as the
one you're referring to, to a local workspace.accdb file. But, I'm not
convinced the "bloat" hit ends up in the temp database, as I think it still
winds up the in the program file. I'll have a look at your link to see if
this helps with the bloat in my main app.
For the suggestions table, one could comment out the openquery line that
delete's all the recs in the suggmatch table.
I also like your idea of positioning the form, as the first thing I do when
spellchecking is to move it out of my way.
I gave a demo of this to my brother, and his favorite part was that it
scrolled and highlighted the words as it checked them, which he hadn't
really seen before. I had a problem where, if it hit a bad word, it would
stop the scrolling when you resumed the check, but a simple DoEvents took
care of that. He also suggested I ignore weblinks, which I added this past
week.
I'm sure there could be speed improvements. In the function that builds
suggestions, I ended up finding the need to add another field to the
dictionary tables for word length. So if you add words manually to the
table, you'll need to add the length as well. As for suggestions, I'll only
look at words that are within a few characters of the length of the
misspelled word. Your suggestion of not wiping out the SuggMatch table each
time could improve speed.
I found on a vista machine, that the 97/2000/2007 versions were all very
fast. On an older xp machine, the speed on the access 97 version won out
(older software always tends to run faster on older hardware. good old
planned obsolescence!)
Thanks again,
Andy
P.S. I did another search last night to see if I can find the same site
where I found the files of words, and couldn't find it within the first 2
page results.
"Tony Toews [MVP]" <tt****@telusplanet.netwrote in message
news:2p********************************@4ax.com...
"ARC" <PC*****@PCESoft.invalidwrote:
On playing around with the utility I have a few more suggestions.
1) Suggestion about the SuggMatch table. I see that is a temporary table
in the FE.
Each time you hit a word you recreate that table to fill the list box.
I'd suggest
using a temporary tables MDB to avoid significant bloating of the FE MDB.
Just
running the sample code in your MDB bloated the MDB by 1.5 Mb.
See the TempTables.MDB page at my website which illustrates how to use a
temporary
MDB in your app. http://www.granite.ab.ca/access/temptables.htm
2) Is it possible to leave that table with all the suggested words from a
to z? So
as to avoid the slight delay when displaying the suggestions? Sure it
will take more
room but what the heck.
3) Now if you wanted to get real fancy, and I wouldn't worry about it for
right now,
is to fetch the top, left, width and height positions of the text control.
then
attempt to position the spell check form so it doesn't overlap the text
control.
I'd further suggest to try to display it lower if possible and then higher
if
possible. If neither are possible then as low as possible so that your
form overlaps
the control but doesn't go below the bottom of the Access window.
I quite like the look and feel of your utility. I think you've done a
nice,
professional job with it.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
