> G_5583.
>
> AM

Signature
Mit freundlichen Gruessen
Ruben Storm
#########################################################
Storm - NET Heilbronn Tel.: +49 7131 642919 0
Ruben Storm Fax: +49 7131 642919 200
Gartenstrasse 46 E-Mail: office@storm-isp.de
74072 Heilbronn Web: http://www.storm-isp.de
#########################################################
> Ok,
> but what is if the Software does not run without the Database, but it is
> freeware??
First of all, a general disclaimer: for a definitive answer, you should
contact McKoi SQL developers. Having said that, the issue of GPL, or McKoi
licensing has nothing to do with the amount of money you intend to charge
for your product. The only thing that matters here is whether your product
has built-in dependencies on the GPLed software (in this case, McKoi). If
the dependencies do exist, then you have a choice of either releasing your
product under the GPL, or buying a commercial license from McKoi. What you
sell your product for is immaterial.
> The other question is, if i have two versions, one with McKoi and one
> without a database. The one without the database, someone has to setup his
> own Database to use with the software.
>
> What is in that case?
To avoid attracting the GPL, you should have one version of your product
that is free of any dependencies on McKoi. You can have an ASCII file that
spells out the name of the JDBC driver, and have your program load it at the
runtime. This way the users can switch from one database to another of their
choosing, and you product's operation does not depend on the presence of
McKoi files in its environment (so long as the users choose another
database).
> The think is that i will work on the Project, as long as that Protect is not
> finished, i will release it as freeware. But the finished one will be
[quoted text clipped - 3 lines]
> lizenz to McKoi, i just recharge it the enduser. But if i have to pay the
> $50 it for every freeware lizenz i distribute, i will be badly broke.
See above. Avoid the built-in dependencies on a particular database (i.e.
use the JDBC and plain-vanilla SQL constructs), and you are free. Make a
direct refence to the proprietory parts of McKoi (or any GPLed product for
this matter) and you are hooked. It all boils down to how you organize your
database-handling code.
> Thanx a lot
You are welcome, but check it out with McKoi developers.