Issue with t_snapshot and t_usys primary columns

[RobG.]

I have successfully managed to get Enterprise Architect working with MS SQL Server and am using transactional replication to allow users to work offsite or remotely without a connection, and synchronie when they are back in the office.

To achieve this, MS SQL Server needs to manage the primary ID's so it can assign and  update ID ranges to remove potential for conflicts, however the t_snapshot table has a VARCHAR primary ID, and as EA is automatically allocating a next ID pattern this is causing conflicts when users are offline.

t_snapshot appears to be used to track auditing, and this is where the issue occurs.

Can a fix/patch be created to create a primary ID for this table that is an INTEGER? I see no reason why any primary ID unless a GUID would need to be textural.

[qwerty]

But EA uses a string (L<num>) as primary key for whatever reason. I doubt that a feature request will be adopted soon in that case.

q.