Wendell;

The main form is bound. The reason for the text boxes is to enable the grid portion of the split form to display properly.

The reason for the split form is the users of this app are familiar/comfortable with the Excel-like functionality of a table showing their data as well as the sorting/filtering functionalities.

This app started out as a VERY simple - as little code as absolutely possible, replacement for an Excel workbook that was being shared by about a dozen people. V1 of this app is now being used by about 100 people regionally dispersed across a province. :w00t: I am the sole data architect and app developer. I am not a developer (or data architect) by profession but am thoroughly enjoying the learning process. I have done lots work with SLQ Server databases for about 15 years (mostly ad-hoc development as well as considerable data mining).

I will see what I can do about posting the DDL to build the DB and a copy of the .accdb file so you can have a better look at what's going on.

The other thing to point out is that some of the combo boxes have cascading dependencies; Team is dependent on Directorate. The four boxes in the Application Class section are dependent, from top to bottom - selecting a Group controls what's available for selection in Category and so on.

All of the reference/look-up tables which support the combo boxes have Effective date and Obsolete date columns to support the business requirement of obsoleting records so that the become invalid for current use so all of the RowSource code must take that into account. This functionality is another reason for the text boxes. The RowSources for the ComboBoxes must be requeried with each record navigation on the main from, except, it doesn't, really.... The only time the RowSource REALLY needs to be refreshed is in the instant before it's used. Hence the code on the gotfocus and mouse move events which builds the RowSource and issues a reqeury. If the user is just browsing records there's no need to be requerying all of those RowSources. This technique has vastly improved the record navigation performance as well as significantly reducing the number of database accesses related to record navigation.

Thanks again for sticking with me on this.