Combining Multiple Small Solutions Into One Larger Solution

Let’s say a developer builds and distributes multiple small Servoy solutions, for example - a Human Resources module here, a CRM module there, and a Help Desk module over there. These modules are stand-alones and distributed as such. All would be using the same database engine (SQLAnywhere for example) but different tables.

SQLAnywhere has the ability to pull together multiple databases into one set of tables. What upfront planning would be recommended to allow the Servoy developer to combine multiple modules with the least amount of headache?

I hope I’m making myself clear.

As Servoy can work easily with multiple database servers I would just let each module use it’s own database.

Along these same lines: is there a way to merge multiple Servoy solutions at this time?

  • david

That’s not possible at the moment but it is a feature we are working on.

jaleman:
That’s not possible at the moment but it is a feature we are working on.

Deploying such a feature could be by letting your own solution check online if someone is illegaly using your solution connecting to or exchanging data with a solution on your own server wich holds serial numbers of your solutions for example.

Is it also possible to share one SQL-dbase with two solutions at the same time?

Bert:
Deploying such a feature could be by letting your own solution check online if someone is illegaly using your solution connecting to or exchanging data with a solution on your own server wich holds serial numbers of your solutions for example.

What’s the relation between this and merging different solutions?

Bert:
Is it also possible to share one SQL-dbase with two solutions at the same time?

Yes