Primary Keys and Upgrading solutions

Hi

I am about to deploy my first solution shortly and would like to confirm my understanding of pk’s. My tables use servoy sequencing to determine the keys and i generally use starting values.

Can you please confirm:

If there is any data to import into a solution before production use after the import, i will have to update the pk starting no. in the developer tool to get the sequencing in the right order for all relevant tables?

While in production any newly imported solution file will not change this original sequence no matter what was specified in the dataproviders of the newly imported solution?

Any data imported while in production use should never map to the primary keys?

rodneysieb:
If there is any data to import into a solution before production use after the import, i will have to update the pk starting no. in the developer tool to get the sequencing in the right order for all relevant tables?

any data?
The only possibility your servoy sequences can get out of sync is when working with something else on the database than only servoy server it self.
if you have more programs working on the same database, use db_ident or db_seq types as sequence.

rodneysieb:
While in production any newly imported solution file will not change this original sequence no matter what was specified in the dataproviders of the newly imported solution?

An import could change the sequence type (but it would ask before doing so)