Inside ASI-AP

In rare circumstances, EFT manages to obtain a non-unique id and thus a database error iss generated.

I have looked further into this and the procedure EFT calls to obtain the Activity.SEQN is sp_asi_GetCounter2 ... and now from the looks of it, the procedure doesn't guarantee a unique value. There is another stored procedure sp_iboGetCounter that does, however it takes different parameters, so there will need to be a recompile of the EFT code to fix this.