ordercheck duplicate keys

[willows]

This contribution works fine but has a worrying little dependency, it presumes you will never edit an order on the good order side. If you do you will knock the indexes out of line. The indexes use increment_next_val in the data base and when you try to move orders when these go out of line you get duplicate key error s and strange behaviour after that.

 

There needs to be on key fix added into this.

 

When the problem order is being moved it needs to not pass the next val keys into the good order area. Let these keys be generated automatically as they should.

The problem order then needs to be deleted after it is moved / locked so as to prevent another move from happening.

 

Cheers

Sean