Hi
Our organisation is using an off the shelf application which has an
Oracle database back-end. We have a licence for 10 concurrent users.
We now need to have additional users access the data for view purposes
only. As the cost of increasing the licence count is prohibitive are
we within the law if we write our own software using VB or something
similar to access the information on the database, without using the
paid for app. As I write this I'm thinking that as the application
provider designed the database they will have some say in whether we
can use our own software to access it. But it is our data so would
that be our copyright?

I know the question is a bit vague but any suggestions would be
appreciated. Thanks.

On 04.01.2008 11:01, Steve wrote:
Are you talking about Oracle or third party software license here?

You should clarify this with the vendor that supplied this app. I do
not see how this question is related to Oracle. You might have to pay
higher license fees to Oracle based on your license model though.

Then ask /them/. You might face loss of support when accessing this
application's data via other ways than through this application.

Well, this is a completely different question. We do not know your data
nor where it came from. If you do not know the copyright status of your
data how do you expect us to know it?

Indeed. "Vague" seems vaguely understated...

Cheers

robert

On 04.01.2008 11:01, Steve wrote:
Are you talking about Oracle or third party software license here?

You should clarify this with the vendor that supplied this app. I do
not see how this question is related to Oracle. You might have to pay
higher license fees to Oracle based on your license model though.

Then ask /them/. You might face loss of support when accessing this
application's data via other ways than through this application.

Well, this is a completely different question. We do not know your data
nor where it came from. If you do not know the copyright status of your
data how do you expect us to know it?

Indeed. "Vague" seems vaguely understated...

Cheers

robert

On 04.01.2008 11:01, Steve wrote:
Are you talking about Oracle or third party software license here?

You should clarify this with the vendor that supplied this app. I do
not see how this question is related to Oracle. You might have to pay
higher license fees to Oracle based on your license model though.

Then ask /them/. You might face loss of support when accessing this
application's data via other ways than through this application.

Well, this is a completely different question. We do not know your data
nor where it came from. If you do not know the copyright status of your
data how do you expect us to know it?

Indeed. "Vague" seems vaguely understated...

Cheers

robert

On 04.01.2008 11:01, Steve wrote:
Are you talking about Oracle or third party software license here?

You should clarify this with the vendor that supplied this app. I do
not see how this question is related to Oracle. You might have to pay
higher license fees to Oracle based on your license model though.

Then ask /them/. You might face loss of support when accessing this
application's data via other ways than through this application.

Well, this is a completely different question. We do not know your data
nor where it came from. If you do not know the copyright status of your
data how do you expect us to know it?

Indeed. "Vague" seems vaguely understated...

Cheers

robert

On Jan 4, 2:01*am, Steve <stephenal... (AT) hotmail (DOT) com> wrote:
I don't know your situation, but most of the situations I've been in
that have a 3rd party license issue, the 3rd party only cares about
usage through their system. Oracle licensing info can be found on
their website, there are many intricacies possible. When you say "the
law," keep in mind you are normally talking about contract law, which
in the US is governed by uniform commerce codes, what the contract
says, and case law. Black and White may be Grey.

In general, if you are updating things that the 3rd party thinks only
they should update, you are screwed. So if you do that, you need to
be absolutely sure about what you are doing, and don't tell them.

View-only may or may not be an issue, it depends. Software licensing
is a strange animal. Some of the strangest stuff comes from using
licensing from before web-based access was possible, but most current
packages I've seen have some way of dealing with that now.

Sometimes you have to just pay it. Vendors call this "lock-in." I've
seen many situations where a smaller or cheaper system could do fine,
but the new license fees would make it less feasible than just buying
more licenses for the current config.

Nowadays, there's always giving each user XE and imp their data (if it
is small enough) and let them do what they will...

jg
--
@home.com is bogus.
Who owns your social data? http://www.eweek.com/article2/0,1895,2243727,00.asp

On Jan 4, 2:01*am, Steve <stephenal... (AT) hotmail (DOT) com> wrote:
I don't know your situation, but most of the situations I've been in
that have a 3rd party license issue, the 3rd party only cares about
usage through their system. Oracle licensing info can be found on
their website, there are many intricacies possible. When you say "the
law," keep in mind you are normally talking about contract law, which
in the US is governed by uniform commerce codes, what the contract
says, and case law. Black and White may be Grey.

In general, if you are updating things that the 3rd party thinks only
they should update, you are screwed. So if you do that, you need to
be absolutely sure about what you are doing, and don't tell them.

View-only may or may not be an issue, it depends. Software licensing
is a strange animal. Some of the strangest stuff comes from using
licensing from before web-based access was possible, but most current
packages I've seen have some way of dealing with that now.

Sometimes you have to just pay it. Vendors call this "lock-in." I've
seen many situations where a smaller or cheaper system could do fine,
but the new license fees would make it less feasible than just buying
more licenses for the current config.

Nowadays, there's always giving each user XE and imp their data (if it
is small enough) and let them do what they will...

jg
--
@home.com is bogus.
Who owns your social data? http://www.eweek.com/article2/0,1895,2243727,00.asp

On Jan 4, 2:01*am, Steve <stephenal... (AT) hotmail (DOT) com> wrote:
I don't know your situation, but most of the situations I've been in
that have a 3rd party license issue, the 3rd party only cares about
usage through their system. Oracle licensing info can be found on
their website, there are many intricacies possible. When you say "the
law," keep in mind you are normally talking about contract law, which
in the US is governed by uniform commerce codes, what the contract
says, and case law. Black and White may be Grey.

In general, if you are updating things that the 3rd party thinks only
they should update, you are screwed. So if you do that, you need to
be absolutely sure about what you are doing, and don't tell them.

View-only may or may not be an issue, it depends. Software licensing
is a strange animal. Some of the strangest stuff comes from using
licensing from before web-based access was possible, but most current
packages I've seen have some way of dealing with that now.

Sometimes you have to just pay it. Vendors call this "lock-in." I've
seen many situations where a smaller or cheaper system could do fine,
but the new license fees would make it less feasible than just buying
more licenses for the current config.

Nowadays, there's always giving each user XE and imp their data (if it
is small enough) and let them do what they will...

jg
--
@home.com is bogus.
Who owns your social data? http://www.eweek.com/article2/0,1895,2243727,00.asp

On Jan 4, 2:01*am, Steve <stephenal... (AT) hotmail (DOT) com> wrote:
I don't know your situation, but most of the situations I've been in
that have a 3rd party license issue, the 3rd party only cares about
usage through their system. Oracle licensing info can be found on
their website, there are many intricacies possible. When you say "the
law," keep in mind you are normally talking about contract law, which
in the US is governed by uniform commerce codes, what the contract
says, and case law. Black and White may be Grey.

In general, if you are updating things that the 3rd party thinks only
they should update, you are screwed. So if you do that, you need to
be absolutely sure about what you are doing, and don't tell them.

View-only may or may not be an issue, it depends. Software licensing
is a strange animal. Some of the strangest stuff comes from using
licensing from before web-based access was possible, but most current
packages I've seen have some way of dealing with that now.

Sometimes you have to just pay it. Vendors call this "lock-in." I've
seen many situations where a smaller or cheaper system could do fine,
but the new license fees would make it less feasible than just buying
more licenses for the current config.

Nowadays, there's always giving each user XE and imp their data (if it
is small enough) and let them do what they will...

jg
--
@home.com is bogus.
Who owns your social data? http://www.eweek.com/article2/0,1895,2243727,00.asp