Knowledge Base
Knowledge BaseSubject: | Question regaring use of next numbers" |
---|---|
Status |
Resolved |
Product | WireCAD v9 |
Product Level | PRO |
Database Type | SQL Azure |
Build Number (last 4 digits of version) | 17102 |
Upload | No file! |
Message
Lets say i have a next cable number like this IP10056.
To make it tidy, i want to start the next number with IP10101 and number from IP10101 to IP10124,
If i then later "reset" the next number to IP10057 and uses the number IP10057 to IP10100 will the numbering "overwrite" the number IP10101 and mess up the database, or will it skip IP10101 to IP10124, as they are already in use?
To make it tidy, i want to start the next number with IP10101 and number from IP10101 to IP10124,
If i then later "reset" the next number to IP10057 and uses the number IP10057 to IP10100 will the numbering "overwrite" the number IP10101 and mess up the database, or will it skip IP10101 to IP10124, as they are already in use?
15-November-2017 (10:04 AM)
The default behavior is to increment/format/test/increment until an available number is found.
So if the sequence key is IP and the next number in the Next Numbers table is 56, the number would be formatted (based on the project rules), say IP0056 and tested. We query the cables table for a record where the cable number field equals IP0056. If found the Next Numbers table is incremented/formatted/tested until an available formatted number is found.
This behavior can be disabled and the Next Number will win and potentially create duplicates.
See the screenshot.
So if the sequence key is IP and the next number in the Next Numbers table is 56, the number would be formatted (based on the project rules), say IP0056 and tested. We query the cables table for a record where the cable number field equals IP0056. If found the Next Numbers table is incremented/formatted/tested until an available formatted number is found.
This behavior can be disabled and the Next Number will win and potentially create duplicates.
See the screenshot.
17-November-2017 (02:13 PM)