problem with sequence number not getting updated

SUGGESTED

We have an issue when we're busy, the sequence number that is used by our sales order document does not get incremented, so when the next person (or web service) tries to create a sales order, they get an error about how that number already exists.


Has anyone else encountered this, or have any advice on how to prevent it? I suppose I could write a stored procedure that checks every so often to see if the current VALUER_0 in AVALNUM exists as a sales order in SORDER.


Thanks,

- Jim