Database Structure for Workflow Management System

I am building a database that will serve as a workflow management system for 50-75 simultaneous users (150-250 unique users altogether).  In short, my question is: Is there a better way to organize and display the data that I have in a way that multiple users can grab their work items from certain queues, and route/complete them as necessary?  I apologize for length, the rest is a description of what is contained in the database:

The entire database front-end is built around one form, very similar to what I have attached.  The 'Action Queues' section (subform: frmWorkQueueAction) is a continuous form that lists outstanding queues for a specific user based on their production team's ID, that is linked to a table housing queues for each team.  This pulls all "queue" records from that table with a status of "Action".  The 'Follow-Up Queues' is the same as Action queues, with a status of "Follow-up".  This allows me to display two different types of queues; queues that should have action taken on them now, and queues that should have action taken on them if not completed after xx Days (completed by other individuals).

Work Items: [Queue Name] is the header for the "frm_WorkQueue" subform.  That is a continuous form that lists all data from the work items table (tbl_pended_master), and is filtered when "Queues" from the Action/Follow-up section to the left are clicked (code sample below).  This section shows summarized information for each item.  If a Work Item is double-clicked, a popup form comes up with that item's detailed information.  This is where the employee would type comments on the item, and route/complete the file via a combo box.

To give you a quick idea of my table setup, here are the tables used:
tblEmployees; Major Fields Used: EmployeeID, EmployeeName, TeamID
tbl_pended_master: Major Fields Used: UniqueID, DateReceived, EmployeeID, DestinationCode, FileStatus, DateCompleted
**DestinationCode is the system identifier for the "queue" used.  Each code is a different item type, and should have it's own queue.
tblQueues: QueueID, TeamID, DestinationCode, QueueName, QueueType (Action or Follow-Up), ItemStatus, ItemID, FollowUpDays

As stated before, tbl_pended_master is the main table in the database.  This houses most of the information for these files.  Items are identified by DestinationCode and EmployeeID (What they are and who they belong to).  tblQueues runs the two subforms on the left of the image.  TeamID links to the tblEmployee table.  This table allows me to bounce the employee's TeamID up against it to determine which queues they should be able to see.  By clicking these queues, a filter (shown below) is placed on the main subform to show that queue's data.


I'm sure that there's a better way to do this, but I'm not sure where to start.  Anyone have any suggestions?Start Free Trial

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:

'When a Queue is clicked...
Private Sub TotalFiles_Click()
Dim rs As Recordset
Dim TotalItems As Double
Dim strCriteria As String
Dim strStatus As String
strStatus = ""
If Not IsNull(Me.q_Item_Status.Value) Then strStatus = Me.q_Item_Status.Value
 
strCriteria = "[pddt_destination_cd] = '" & Me.DestinationCode & "'"
If strStatus <> "" Then strCriteria = strCriteria & " AND [pddt_status] = '" & Me.q_Item_Status.Value & "'"
 
Forms![frmWorkflowMain]![fsubWorkItems].Form.FilterOn = True
Forms!frmWorkflowMain!fsubWorkItems.Form.Filter = strCriteria
                                                  
Set rs = Forms![frmWorkflowMain]![fsubWorkItems].Form.RecordsetClone
If Not rs.EOF Then
rs.MoveLast
TotalItems = rs.RecordCount
rs.MoveFirst
End If
rs.Close
Set rs = Nothing
 
Forms!frmWorkflowMain!lblWorkItems.Caption = " Work Items:  Destination " & Forms![frmWorkflowMain]![fsubWorkQueues].Form![DestinationCode] & ", " & TotalItems & " total items"
End Sub