If you do not share this database over the network, there are ways to use the Maximum docket number + 1 to assign the next number in the series, but I suggest a change in design of your database:
Projects::ProjectID = ProjectWorkRecords::ProjectID
You only have one record for each project in the projects table so now an auto-entered serial can be used to enter serial numbers into Projects::ProjectID, but your ProjectWorkRecords can use the same ProjectID Repeatedly to log work performed on the same project.
Thanks for the quick response!
I am actually sharing this database with a manager over the network, so does that impact your answer? Also, if you could walk me through the specific steps I need to take, I would appreciate it more than life itself. Thanks.
My approach to this would be to keep the next Docket number as a field value in a control table and script the creation of the docket number based on the Docket type (new or Duplicate) and set the field to that value then advance the control field value. You may have to do some error checking to be sure the values stay in sync.
Someone else might have a better ides though