Aha, it looks like I fixed a different problem. It is the Servoy REPOSITORY which contains information about the sequences on tables, not the database. Unfortunately when you create a CLEAN repository, this means that all primary keys are set to the default, namely Servoy sequence. (There is no other way to go about this. See Note 1.)
When you then import your solution, it actually DOES what you ask!! Namely, it sees that the tables already HAVE sequences in the repository, and does NOT override them with the values found in the import. Therefore, all your tables will end up with Servoy sequences.
What I can do, and I cannot think of any other solution, is to give the user the CHOICE to OVERRIDE sequences when doing an import. Note that this very dangerous, since OTHER solutions could be using these tables/columns as well.
Thus normally you would like to leave existing sequences in a repository as the are, unless you are creating new tables (and this is, what Servoy currently does). However, in your case you want to OVERRIDE the existing sequences, and that currently is not an option. This is what I will add.
Here I think it is best that I ask once per server that the solution uses, if it should override sequences (should the question arise). Asking for every column will result in having to do 1000 clicks, and not asking per server is too coarse grained.
Is this a good solution for you?
Note 1: Actually there is a possible solution for this as well, namely it could be possible to specify the default sequence for a server in the servoy.properties file. This default could be either Servoy sequence or db identity. (Note that it CANNOT be db sequence, since there is no way we can tell WHICH sequence should be queried for inserts). I will consider adding this option as well.