Hello all,
While digging the forum for all kind of 3.55 server-making/maintaining tips, I've found this thread.
Not sure if it's a good solution what I was thinking about (I'm at work right now and can't test it on my home PC) but...to find out which is the duplication (correct term?) maybe can check some autoincremental ID. Now I don't know the exact structure of the table, but if this cannot be applied, maybe a small change to the structure will help (if it works with MSSQL): adding a new column, with the "timestamp" type which is updated every time an operation occurs on that record. So the newest record is the duplication of the original.
Is this applicable?
Anyway I will try this at home, even if I don't know how to replicate the situation when dupped items appear
LE: nevermind, the records are inserted when logout action occurs so the idea is useless
While digging the forum for all kind of 3.55 server-making/maintaining tips, I've found this thread.
Not sure if it's a good solution what I was thinking about (I'm at work right now and can't test it on my home PC) but...to find out which is the duplication (correct term?) maybe can check some autoincremental ID. Now I don't know the exact structure of the table, but if this cannot be applied, maybe a small change to the structure will help (if it works with MSSQL): adding a new column, with the "timestamp" type which is updated every time an operation occurs on that record. So the newest record is the duplication of the original.
Is this applicable?
Anyway I will try this at home, even if I don't know how to replicate the situation when dupped items appear
LE: nevermind, the records are inserted when logout action occurs so the idea is useless
Last edited:
