cascading combo boxes

[RuralGuy]

How about my post #13?

[SunTop]

RuralGuy: their is no space in my code, that was just a typo in the post, probably because I copied it and past it from my previous post

Micron: I did not use (docmd.setwarnings false) anywhere in my code, I never knew it existed till just now. I use this form to alter existing records which rarely happens (but it happens so I have to provide it in the database)

[RuralGuy]

I'm almost out of ideas. What is the RecordSource of your form? Query, Table, Query with a Join, SQL string (dynamic query)?

[John_G]

Does combo2 have an After Update event on it? If so, you could try running that event from your code in combo1 After Update: combo2_afterUpate

How do you that the value in the underlying table field is not being changed when you set Combo2 to Null?

But a more important issue is that even if you can set the value in combo2 and the field to Null, it's going to give you an error because the field is required. However, you should not see that error until you try to save the record; the error is coming from the Validation rule on the table field. You don't need it anyway - setting required = Yes will do. You could use Before Update at the record (form) level to stop a record update if the user did not select a value in Combo2.

One other thing to check is the Limit To list property of Combo2. If that is set to Yes, you can't set combo2 to Null because it would violate the Limit to List.