Subject | Re: Firebird Name / Service / exe |
---|---|
Author | philcaetano |
Post date | 2006-11-19T13:48:45Z |
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
existing database. I was meant to rename it to the name of our
product so that it would look like 1 package deal(example. ABC and ABC
Engine). Which is more accepted. The key word is not to call it a
"Database" engine. Even if it is one. Like I said, its a very silly
issue. And its becoming a growing issue. IT departments are starting
to get "lazy" or "God like attitude" and don't want deal with the
possible issue of support anything else that isn't on their "certificate".
>Then I should be more clear too. I never meant to rename it to an
> --- In firebird-support@yahoogroups.com, "Ann W. Harrison"
> <aharrison@> wrote:
> >
> > Adam wrote:
> I should have been more clear. I did not envisage any legal hurdles
> for making such changes from the Firebird end. But if you made a
> custom build and called it 'Microsoft SQL Server', then you have just
> infringed trademarks owned by Microsoft (at the least), you are
> possibly also guilty of fraud, and really in trouble if you have
> charged license fees on the basis of them being supplied SQL Server
> licenses.
>
> Adam
>
existing database. I was meant to rename it to the name of our
product so that it would look like 1 package deal(example. ABC and ABC
Engine). Which is more accepted. The key word is not to call it a
"Database" engine. Even if it is one. Like I said, its a very silly
issue. And its becoming a growing issue. IT departments are starting
to get "lazy" or "God like attitude" and don't want deal with the
possible issue of support anything else that isn't on their "certificate".