License issues with OWC11

[Developers Club]

I've read the following article:

How to deploy the Office 2003 Web Components in an Office 2003 program,
reviser a fondo.
http://support.microsoft.com/default.aspx?scid=kb;en-us;828950

The parts that I'm more interested in are:

"By default, if you do not have Office 2003, Access 2003, Excel 2003,
or FrontPage 2003 installed on the computer, you are licensed for
static, non-interactive use of the Office 2003 Web Components program
when you install the Office Web Components. With this kind of license,
you can view the controls on a Web page, but you are not licensed to
interact with the controls. If your organization owns an Enterprise,
Select, or Maintenance Agreement for Office 2003 and you plan to deploy
Office 2003 in phases, you can allow early adopters of Office 2003 to
share component-based Web pages with users who have not yet installed
Office 2003."

Here everything is good. I've developed a site that uses OWC and if the
client didn't have OFFICE he could see the page in non interactive
mode, and of course if he has he could see in interactive mode.

"With the release of Microsoft Office 2003 SP2, the license checking
code was also removed for Microsoft Office Web Components version 11.
If your organization downloaded an updated version of Office Web
Components version 11 after the release of Microsoft Office 2003 SP2,
you will no longer have the license checking code in Office Web
Components version 11."

Now this is, what I don't like in part, if someone download the OWC11
now has the full interactive mode, regardless he have or doesn't have
Office installed?

What should I do? What is the meaning of this? Any help would be
appreciated.

Should I shut down the site because I can't control wheter a user uses
interactive or non-interactive mode??

 

[Alvin Bruney [MVP]]

Based on the licensing rules, you have to make a decision about compliance.
I am pretty sure no one in here will make that decision for you.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin

 

[Developers Club]

Thanks for your reply.

Now what I want to know is if my interpretation of the licensing rules
are correct.

Before when the control had the license checking code, it was possible
to develop with OWC and you as developer wouldn't have to worry about
the clients who would use the OWC, because if the clients didn't have
office then he could still use the control in non-interactive mode
without infringing any rule, all of this was controlled by the control.

Now, without the license checking code, it isn't possible to develop
using OWC if you don't know for certain who will use the OWC, if you
are sure that all of your clients have OFFICE installed, then you can
develop with OWC and if you don't know then you shouldn't deploy the
application.

Knowing if my interpretation is correct would help me in making the
decision.
I'd like the control when the control itself controlled if the client
had a valide license, now it seems that the developers have to know
this before deploying the application.

Thanks in advanced.

 

[Alvin Bruney [MVP]]

Obviously, I can't give you an answer on this because it would bind me
legally and I cannot speak for Microsoft.
I would strongly recommend you open a support ticket to confirm your
suspicion. (Reread this carefully.)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

Thanks for your reply.

Now what I want to know is if my interpretation of the licensing rules
are correct.

Before when the control had the license checking code, it was possible
to develop with OWC and you as developer wouldn't have to worry about
the clients who would use the OWC, because if the clients didn't have
office then he could still use the control in non-interactive mode
without infringing any rule, all of this was controlled by the control.

Now, without the license checking code, it isn't possible to develop
using OWC if you don't know for certain who will use the OWC, if you
are sure that all of your clients have OFFICE installed, then you can
develop with OWC and if you don't know then you shouldn't deploy the
application.

Knowing if my interpretation is correct would help me in making the
decision.
I'd like the control when the control itself controlled if the client
had a valide license, now it seems that the developers have to know
this before deploying the application.

Thanks in advanced.

Based on the licensing rules, you have to make a decision about
compliance.
I am pretty sure no one in here will make that decision for you.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin

 

[Developers Club]

Thanks again, that's what I'm gonna do.

Obviously, I can't give you an answer on this because it would bind me
legally and I cannot speak for Microsoft.
I would strongly recommend you open a support ticket to confirm your
suspicion. (Reread this carefully.)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

Thanks for your reply.

Now what I want to know is if my interpretation of the licensing rules
are correct.

Before when the control had the license checking code, it was possible
to develop with OWC and you as developer wouldn't have to worry about
the clients who would use the OWC, because if the clients didn't have
office then he could still use the control in non-interactive mode
without infringing any rule, all of this was controlled by the control.

Now, without the license checking code, it isn't possible to develop
using OWC if you don't know for certain who will use the OWC, if you
are sure that all of your clients have OFFICE installed, then you can
develop with OWC and if you don't know then you shouldn't deploy the
application.

Knowing if my interpretation is correct would help me in making the
decision.
I'd like the control when the control itself controlled if the client
had a valide license, now it seems that the developers have to know
this before deploying the application.

Thanks in advanced.

Based on the licensing rules, you have to make a decision about
compliance.
I am pretty sure no one in here will make that decision for you.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin

 

[Cuware]

Obviously, I can't give you an answer on this because it would bind me
legally and I cannot speak for Microsoft.
I would strongly recommend you open a support ticket to confirm your
suspicion. (Reread this carefully.)

This sounds like a serious systems deployment problem
and problem for intranet OWC developers.

If some users have the license checking and others don't,
(depending on when they installed OWC-11/Office)
is there an approved systems or app developer method
for handling all the users uniformly?

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

Thanks for your reply.

Now what I want to know is if my interpretation of the licensing rules
are correct.

Before when the control had the license checking code, it was possible
to develop with OWC and you as developer wouldn't have to worry about
the clients who would use the OWC, because if the clients didn't have
office then he could still use the control in non-interactive mode
without infringing any rule, all of this was controlled by the control.

Now, without the license checking code, it isn't possible to develop
using OWC if you don't know for certain who will use the OWC, if you
are sure that all of your clients have OFFICE installed, then you can
develop with OWC and if you don't know then you shouldn't deploy the
application.

Knowing if my interpretation is correct would help me in making the
decision.
I'd like the control when the control itself controlled if the client
had a valide license, now it seems that the developers have to know
this before deploying the application.

Thanks in advanced.

Based on the licensing rules, you have to make a decision about
compliance.
I am pretty sure no one in here will make that decision for you.

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin

 

[Developers Club]

I can't find a License Document for the OWC.
¿Can someone know where it is?
Especially one that adresses the deployment issues discussed in this
thread.