Re: Spell checking problem
I may be wrong, but I think the client machine does need to have Office Installed, If you create a word object in your VB project.
As said, I'm not 100% sure :ehh:
Re: Spell checking problem
Quote:
Originally Posted by HanneSThEGreaT
I may be wrong, but I think the client machine does need to have Office Installed, If you create a word object in your VB project.
As said, I'm not 100% sure :ehh:
Yes Hannes, you are totally right. All this office parts needs to have the licenced appl. on the machine otherwise the olb's would not work. In my understanding this .olb' s are like a 'bridge' which connects VB programs to the application which are needed. Its a lot of work to find out which dlls are needed to get it working without having full appl on machine and its not legal, to use code created by others, without having licence to use it.
Mvnrajan If an application needs to be independend, then you cannot use codeparts (.olb .ocx .dll' s... ) which are not part of the normal VB sghipping package, which make the application depending on the existence of something. Thats a contradiction in se. If you have to be independed then you have to create your own spellchecking system. And then maybe its cheaper to get the people to buy word together with your application instead of doing thousend of man-hour for creating a new spellchecking system. I dislike to be the 'bringer of bad news' but in that case its just as told. Take it easy. You can put it on the label of your programs casebox, needed prerequirements: WinXP, Win 2k,Win 98 ...... Word2000 or up.. something like that
Jonny Poet