By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,695 Members | 1,221 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,695 IT Pros & Developers. It's quick & easy.

Is Office required on End user's PC ?

P: n/a


I've been developing an app that makes use of MS Word 11 Object
Library, it creates a Word.Application, loads a doc and prints it, and
it works very well on several PCs we have here that have Office 2003
installed.

I've installed it (using ClickOnce) on a new PC without office, and
the app works fine, except when it comes to do some printing using the
above mentioned thing. it says it can't create activeX object.

If I were to install Office 2003 on it, it would work fine no doubt.
Is this right? I was under the assumption that I could distribute the
nessesary files for it to work on any PC, regardless of whether it has
Office installed.

If this is the case, what references should I have in my project?
I have:
Microsoft.Office.Core
Word

Are these the only two I need?
Scott
Feb 9 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
>If I were to install Office 2003 on it, it would work fine no doubt.
Is this right?


Yes, you need to install Office on the client.
Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.
Feb 9 '06 #2

P: n/a
"Scott H" <x@x.com> schrieb:
I've been developing an app that makes use of MS Word 11 Object
Library, it creates a Word.Application, loads a doc and prints it, and
it works very well on several PCs we have here that have Office 2003
installed.

I've installed it (using ClickOnce) on a new PC without office, and
the app works fine, except when it comes to do some printing using the
above mentioned thing. it says it can't create activeX object.

If I were to install Office 2003 on it, it would work fine no doubt.
Is this right?


If your application uses the Word object model, Word must be installed. In
addition to that, note that applications started directly from the browser
do not have all permissions (this is indicated by the small yellow
exclamation mark in the application's title bar).

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Feb 9 '06 #3

P: n/a

Thanks for your replies.
So, a follow up question would be... any recomendations as to do this an
alternative way, I was thinking maybe using Crystal reports, but before I
do, will it install everything with my app to make it display and print
the reports, or will the end-user need to buy that too?

All I really need it to do is have templates that the user can edit, Eg.
change the header with their own company logo. Then my app would fill in
various parts of the templates with data from a SQL server, and then
either display them on screen or print them.

I've never used crystal reports before in VB, dispite having been
programming in VB for about 8 years :-)

Scott H


On Thu, 09 Feb 2006 23:16:39 -0000, Herfried K. Wagner [MVP]
<hi***************@gmx.at> wrote:
"Scott H" <x@x.com> schrieb:
I've been developing an app that makes use of MS Word 11 Object
Library, it creates a Word.Application, loads a doc and prints it, and
it works very well on several PCs we have here that have Office 2003
installed.

I've installed it (using ClickOnce) on a new PC without office, and
the app works fine, except when it comes to do some printing using the
above mentioned thing. it says it can't create activeX object.

If I were to install Office 2003 on it, it would work fine no doubt.
Is this right?


If your application uses the Word object model, Word must be installed.
In addition to that, note that applications started directly from the
browser do not have all permissions (this is indicated by the small
yellow exclamation mark in the application's title bar).

Feb 10 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.