Shipment # jumped to a higher range (DNP)

Problem:  The shipment number has jumped to a much higher sequence range.  For this example it jumped from 161006 to 190807

Cause (if known): Bad index

Solution:

Had everyone get out of Horizon

Re-indexed Dispatch & Billing
Had all users exit Horizon
Made backup of sysdata.dbf
Opened FDW
type USE SYSDATA SHAR and press enter
type BROW FIELDS SYSID, INT1, INT2, NUM1 and press enter
The above will open the database and give you a list of records that will look like a spreadsheet. The fist column header will be SYSID. Arrow down and highlight the DI record. INT1 is the load number (shipment number), INT2 is the manifest number and NUM1 is the trip number.
In this case we only needed to reset the load number so we changed the number in the INT1 field to be the next sequential number (in this case 161007).
Ctrl+W to save
Quit
Had customer enter a new load to verify it was using the correct numbers (it was) and advised that he refuse the 190 loads and re book them.