Search results

Thanks Bob!

Here is the db. If you use the drop down and go to a case number not in the tblCaseDetails, then it will prompt you to add it to the form. Oh, and be gentle with me, I am not a vba guy or anything else for that matter. I am just a grunt firefighter trying to help our department.

I placed the code in the proper place, but I still do not get a refresh. I am going to chop down the db and see if I can upload it.

Bob, Could the issue be with this code that I have in my combo box to check if the ID is in the table (tblTimeline) and if not, then it will add it to the form? Private Sub cboCaseTimeline_Click() Dim intAnswer As Integer If IsNull(Me!cboCaseTimeline) Then Exit Sub With...

The after update of the combo box that is on the main form

Ok, I decided to create a new db and import everything into it from the old db. The error message has now gone, but I have to select the ID twice in the drop down to get the subform to populate. Not sure if I still need to change the reference to the subform or not.

Yes, the subform control and subform are the same name. The article was an interesting read. This is what I have in the combo after update event: Me.sfTimeline.Form.Recordsource = "QCallIncidentDate" Hmmm, nothing seems to work.

Bob, I did as you described and now I get an error message: Method 'Form' of object _subform failed

Thanks for the response Bob! So are you saying to change the recordsource by creating another query and then reference it in the afterupdate event of the combo box?

Ok, I have tried to get my subform to requery and for the life of me, I cannot get it to work with code, but it will work with the F9 key. Main form - frmCaseTimeline subform - sfTimeline combo box - cboTimeline Main table - tblCaseDetails 2nd table - tblCaseTimeline I have frmCaseTimeline...

Ok, I guess I dont have it work correctly, darn. I did get the error to stop, but now whatever record I click on in the cbo I get the message box telling me that the record is not there, which it is. Would it have to do with the cbo reference? .FindFirst "CaseNumber = """ &...

Man, I must not have had enough coffee, lol. I just realized that I was trying to reference a control and I really needed to reference the table, arrrgh! Sorry to waste a thread guys!

Hi guys, Ok, this is what I have: I have setup my main form with 2 subforms to mimic a split form; this works fine. To search for a record, I am using a cbo on the main form which I would like the user to select from. Once selected, then this will populate the first subform. This is the...

jz, sorry for the delayed response, been out of town. I'll work with your idea of the combo box when I get back to the office on Tuesday! I still have the example db that you made up for the junction box and I will try to incorporate this into my form.

I take it to mean that if one person should file many complaints? I have attached the revised tables to what you have advised. Let me know if they look correct to you. Also, I tried to enter the data from my form and the two tables populated as they should, but the junction table was blank.

jz, there is the possibility that there could be more than one complainant per complaint, but the probability of that happening is very low. Should I have the main table (Complaint) setup with another pk (ComplainantID) so that there will be a one (Complaint) to many (Complainant)...

jz, I apologize. I am terrible at explaining what I am trying to accomplish. The form is data entry only. The form is when a complaint is received. I noticed that even though the tables are linked in a relationship, that when information is entered in the Complainant table (via the...

Our PSU bureau currently uses excel to keep track of complaints and complainants. Each complaint is assigned a case number, which is then assigned to the complainant. So far, they have been lucky and no one has entered in the wrong case number to the complainant. With the combo box, I feel...

jz, your solution worked great, but how do I limit what the user can select in the combo box so that they do not select the wrong ComplainantID?

I think I found the mistake! Yes, it is confirmed. I did indeed found the mistake.