F
FBxiii
Hi. I think I know the answer to my question, I just dont know the solution!!
I have got a form that also contains a sub-form. The user inputs
information onto the form/subform and the record saves into the relevant
tables. The user can then do what they need to do and update the record to
Complete.
I designed the form to have a RecordSource, showing all records from a table.
As the table has got 'fuller' it is becoming increasingly difficult for the
users to look through the records for In-Complete work. To overcome this I
have added a Combo-box to allow the user to change views between In-Complete
and Complete jobs. This is done in code after the combo box is updated and
the record source is re-assigned. i.e. Me.RecordSource = "SQL Statement"
Since adding the combo-box, the data is no longer being saved to the tables.
I think it is because the form is now 'Unbound' but I cant be sure.
Can anyone help me overcome this? A record is deemed In-Complete when the
Complete_Date field is Is Null, and Complete when it Is Not Null.
Cheers, Steve.
I have got a form that also contains a sub-form. The user inputs
information onto the form/subform and the record saves into the relevant
tables. The user can then do what they need to do and update the record to
Complete.
I designed the form to have a RecordSource, showing all records from a table.
As the table has got 'fuller' it is becoming increasingly difficult for the
users to look through the records for In-Complete work. To overcome this I
have added a Combo-box to allow the user to change views between In-Complete
and Complete jobs. This is done in code after the combo box is updated and
the record source is re-assigned. i.e. Me.RecordSource = "SQL Statement"
Since adding the combo-box, the data is no longer being saved to the tables.
I think it is because the form is now 'Unbound' but I cant be sure.
Can anyone help me overcome this? A record is deemed In-Complete when the
Complete_Date field is Is Null, and Complete when it Is Not Null.
Cheers, Steve.