Hi,

I have hit a problem with SQL replication and the Identity primary keys on the security BOs. Is there a way of trapping when a new security record is added and replacing the primary key value in program code. Ideally, I would like to avoid doing this through a SQL default column value and handle it entirely within the application.

Thanks in advance.

Aaron

Well....not really on the client side.  You could add a trigger on the SQL table to stuff the new PK into a temp table that you then turn around and query to pull from....but that may be more energy than you are wanting to get into.