November 19, 2020 at 1:38 pm
Hi,
Can someone tell me how to integrate Microsoft Words Spell Checker in SQL SERVER REPORT BUILDER 3.0.
Is it possible in the CODE section of your report to write a function to integrate with a library or something in MS WORD so i can pass in a word from a string field in a table and it highlight in red or something.
Ideally i want to integrate the SPELL CHECKER in SQL SERVER 2016 when i write my script if thats possible at all?
I've been asked to report only rows in table where ASSSET_DESCRIPTIOn text field has spelling mistakes in it if possible plz.
Not Delphi Just the tools REPORT BUILDER 3.0 & SQL SERVER 2016 please.
November 19, 2020 at 2:56 pm
I am not 100% sure, but I am about 95% sure that that is not possible and would be a HUGE performance hit to go that route anyways. A better option (in my mind) would be to either build the SSRS report and export to excel to do spell check OR connect Excel to the SQL table directly and run a spell check on the results.
Alternately, building a spell check into the application that populates the ASSET_DESCRIPTION field would be another solution.
SQL Server definitely doesn't have that built in as (as far as I am aware) it has no highlighting of result sets. You MAY be able to build a custom component to SQL Server to allow some indicator of misspelled words (like appending a * to the end of any misspelled words), but again, it is going to be a painfully slow process.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
November 19, 2020 at 4:23 pm
Thanks Brian for your advice.
I've just looked into the EXCEL linking option and thanks thats interesting to know how to do it after reading.
They ideally wanted me to do a total in text box. I.E. Found 500 lines with problem, and show the 500 lines for them.
I think they will just have to export to word/excel as you say and run a spell checker.
I don't think i can automate anykind of spell checker easily before its exported to word or excel by sounds of it.
November 19, 2020 at 6:01 pm
I imagine you could build up a DLL that could handle it and do some magic on the SQL side, but it is not going to be a quick operation.
Alternately, if you HAD a table of valid words, you could do an EXCEPT on that in your SQL query, but then you are going to need to maintain a list of valid words in the database. And what will make it much more difficult is I expect Asset_Description is going to be one or more sentences, so now your comparison needs to check every word in that column. So from the SQL side, you are now needing to split the string out to an unknown number of words and then find the words that don't exist in your dictionary.
So, not impossible to do, but it would be horribly inefficient on the SQL Side and painful to maintain the dictionary table.
I decided to look into alternate options and there are some messy solutions:
https://stackoverflow.com/questions/7505970/spellcheck-data-in-sql-server <-- use MSAccess or write your own CLR to call the spell checker in Word
That being said, I would just dump the data out to Excel and use the built-in spell check there. The other tricky thing is when something appears misspelled even though it is spelled correctly such as a company name or a specific product or application name. Nice thing about doing it in Excel/Word is you can add the word to the dictionary and you are done; that word won't show up as spelled wrong again. If you use CLR or some large dictionary table to show a report of words spelled wrong, someone needs to manually go in and edit things to say it is spelled correctly.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply