Just to make sure I have understood the licensing scheme clearly, can anybody confirm that:

• A license is required to run the designer and generate a project
• No license is required to run the generated project, be it on 500 servers
• As a contractor, I can create an application using the designer (assuming I own a license) and deliver it to a customer, who will then be able use it without any license being required.

Keeping in mind that the database drivers licensing is another problem, i.e. my customer might have to buy licenses for the database driver for each and every server the application is running on.

I am correct?

sgay wrote:

Just to make sure I have understood the licensing scheme clearly, can anybody confirm that:

• A license is required to run the designer and generate a project

Yes

• No license is required to run the generated project, be it on 500 servers

Correct, the runtime libraries and generated code don't have a runtime fee, they are royalty free.

• As a contractor, I can create an application using the designer (assuming I own a license) and deliver it to a customer, who will then be able use it without any license being required.

Correct.

Keeping in mind that the database drivers licensing is another problem, i.e. my customer might have to buy licenses for the database driver for each and every server the application is running on. I am correct?

No, database drivers are used by the designer. All files used by the designer require a license. Generated code and runtime libraries aren't used by the designer. SQL is generated by Dynamic Query Engines (DQEs) which are assemblies part of the runtime libraries (the DQE dlls) and therefore are royalty free. The drivers are part of teh designer and are used to create/update projects in the designer.

This also applies to the fact when you use the command line tools for refreshing and code generation: you then use parts of the designer and therefore need a license when you operate these tools.

So rule of thumb: the OUTPUT of the designer and the runtime libraries are free from royalty fees and don't require a license. The designer and files it uses do require a license.

Otis wrote:

sgay wrote:

Keeping in mind that the database drivers licensing is another problem, i.e. my customer might have to buy licenses for the database driver for each and every server the application is running on.

No, database drivers are used by the designer. All files used by the designer require a license. Generated code and runtime libraries aren't used by the designer. SQL is generated by Dynamic Query Engines (DQEs) which are assemblies part of the runtime libraries (the DQE dlls) and therefore are royalty free. The drivers are part of teh designer and are used to create/update projects in the designer.

This also applies to the fact when you use the command line tools for refreshing and code generation: you then use parts of the designer and therefore need a license when you operate these tools.

So rule of thumb: the OUTPUT of the designer and the runtime libraries are free from royalty fees and don't require a license. The designer and files it uses do require a license.

Mmm... By "database drivers" I meant something like CoreLab's driver for MySQL. My customer does not need any LLBLGen license as long as it simply uses my application (because all I give to him is the OUTPUT of the designer and the runtime libraries), but he might need CoreLab's licenses. Right?

Makes sense to me, but said customer is not so happy about the CoreLab licenses.

sgay wrote:

Otis wrote:

sgay wrote:

Keeping in mind that the database drivers licensing is another problem, i.e. my customer might have to buy licenses for the database driver for each and every server the application is running on.

No, database drivers are used by the designer. All files used by the designer require a license. Generated code and runtime libraries aren't used by the designer. SQL is generated by Dynamic Query Engines (DQEs) which are assemblies part of the runtime libraries (the DQE dlls) and therefore are royalty free. The drivers are part of teh designer and are used to create/update projects in the designer.

This also applies to the fact when you use the command line tools for refreshing and code generation: you then use parts of the designer and therefore need a license when you operate these tools.

So rule of thumb: the OUTPUT of the designer and the runtime libraries are free from royalty fees and don't require a license. The designer and files it uses do require a license.

Mmm... By "database drivers" I meant something like CoreLab's driver for MySQL. My customer does not need any LLBLGen license as long as it simply uses my application (because all I give to him is the OUTPUT of the designer and the runtime libraries), but he might need CoreLab's licenses. Right?

yes.

Makes sense to me, but said customer is not so happy about the CoreLab licenses.

that's what we can offer for MySql. MySql Inc is the one who's acting silly. They should release their library under the LGPL so everyone who wants to use their database can do so under normal conditions. Now it's not possible and with this policy they force people to either by their own very expensive provider licenses or buy a 3rd party license, e.g. from corelab.