Combo box query (slighlty complicated)

[Rob W]

Greetings,

Bare with me on my explanation, its kinda tricky.

The user would like ONE screen to add and edit information.

The screen is as follows :-

Main form (source is the tblModule)
Module Name
Module ID
Archive (checkbox)

2 Subforms selecting data based on the Module ID.

FOUR navigation buttons FIRST, LAST, NEXT and PREVIOUS.
NEXT button will add a record (if at the end of the recordset).
EDIT they can simply overtype information and use the NEXT button for the
changes to be saved.

However if there are 200 modules and they simply one to edit some data they
would currently have to navigate to the record using the navigation buttons.

Im looking for a solution to add to the 'ease of use' of the application.

Should I use a FIND button ? not sure how this would work if modules had
similar names .. and would rely on user identifying name or id.

Or I did think about using a combo box for Module name selection (they wont
always be able to identy module from its id) but then I would have to set
all the values on the form to be those from the query used in the combo box
and therefore not be bound to the table anymore.

Does anyone have a suggestion how to do all this from within one screen?
I dont want to use the datasheet view either to display ALL details.

Hope this makes sense
Rob

 

[John W. Vinson]

Or I did think about using a combo box for Module name selection (they wont
always be able to identy module from its id) but then I would have to set
all the values on the form to be those from the query used in the combo box
and therefore not be bound to the table anymore.

Um? Why should that be the case? If the ModuleID is the Primary Key of the
table (as it presumably should be), you could have an *unbound* combo box on
the form displaying the module name but with the ModuleID as its bound column.
If you use the Combo Box Wizard to create this combo, you can choose the
option "Have this combo box find a record" - this will put code in the combo's
AfterUpdate event to navigate the form to the record for the selected module.

If you need to build this code manually post back with relevant fieldnames,
it's pretty easy.