Recent content by tbbrown32

I put the code in the OnCurrent event and it works perfect! Thanks for the assistance and the help with the code. I've spent a long time trying to figure this out, so this help is very much appreciated!

Yes that's basically it. I get my terminology mixed up, but the combo boxes started off unbound. CmbClass is now bound to ClassificationID, which seems to work fine and it updates from record to record as well as writing the FK to the Incidents table. As you stated, cmbType is only used to...

Just to further clarify, my SQL code for cmbType is below. I think the reason the requery doesn't work is due to the SQL I'm using. However, since it's a cascading combo box, I can't really alter the SQL query to get what I want I don't think. It needs to use this SQL to pull in all the choices...

It could be operator error on my part. I've been known to do that.

I have tried it several times before I ever posted on this forum, to no avail.

Unfortunately, the requery OnCurrent doesn't update the combo box for me. I tried that, but to no avail.

It is an issue with the combo box not updating. I am using cascading combo boxes, and they work just fine. The issue is that cmbtype does not update when the record changes. So yes, it is a selection, not a write but I do need the combo box to update when the record changes. Sorry for the...

That's correct that it should not be editable, which is why it is only for selection, not writing. I was trying to use Type to filter Class so that the user doesn't have to scroll through 75-100 choices to find the right one. Class is the only field that is written to a table, Type was just...

Thanks MarkK, that solution should work with the exception of the fact that the users are asking for a dropdown instead of a textbox. CmbClass being bound to ClassificationID works great! I just need to find a way to keep CmbType as a dropdown, if that's possible.

Yes, the second combo box is getting the filtered results, that part of it works correctly. It's the first combo box that fails to update as the InternalIncidentID changes. I'll update the code so that the names have a meaning instead of just using the default names.

Sort of a brain fade! I changed the name of the combo boxes in my description because I thought it might be easier for people who aren't familiar with my database to use for reference. The actual combo box names line up with what's in the code. They're combo700 and combo698 in reality. Combo698...

Following the guidelines to prevent cross posting inappropriately, I just want to be clear that I posted a sort of similar issue in another forum. The initial problem I had was sort of resolved, but as a result I am now running into another issue that I alluded to at the end of the other post...

thanks for the information CJ_London, I wasn't aware of the issue with cross posting but as you've now made me aware, it won't be happening again. Thanks again for the info

I have 3 tables, tblIncidents, tblEmployees, and tblIncidentEmployees. In order to enter data into tblEmployees and associate an EmployeeID with an IncidentID in the associative table, I have a form bound to EmployeeID. On this form I have a subform also bound to EmployeeID that contains a combo...

I added the four fields to tblIncidents table per your suggestion. It fits what the user wants and makes the most sense to avoid a lot of additional code. I will post back if it gets sluggish, but so far so good. Thanks again for all the help!