Ok... I understand what you're saying but...
Maybe you're tackling the problem from the wrong direction - what you're talking about is orphaned records
When you delete the rowsource record (number 2) should the delete procedure fix any references to it?
What if it was modified from 2 to 10? I think all the 2's should be changed to 10

I don't agree with you that the combo should show the record which was there before it was deleted (well.. put it this way I can't think of an application for this functionality)

If you really want this behaviour then you can try setting the value property to the controlSource.value maybe in the init of the control (untested)

or.. wait and see if anyone else has a suggestion..


HTH

Will

>I understand what you mean...but this isn't really my problem. The value isn't really deleted. Here is an example that might help.
>In my combobox I have this for the rowsource...
>1
>2
>3
>
>So lets say I pick the value 2....so now the table that is the CONTROL SOURCE has a value of 2....right?
>
>Well..then later the table that is the rowsource is changed...at it just has this:
>1
>3
>
>So the 2 is still in the table that is the control source, right?
>
>But now...when the form is run...you don't see the 2! All you see is a blank. Now even though they can only select a 1 or a 3...the user still needs to be able to see the 2 because that is the current value of the table that is the control source...SURLY there is a way to do this...I'm tempted to make a textbox on top of the combobox to get around this...but that seems kinda like a lot of work and somewhat insane..heh...
>
>ANYHONE got a way around this?