>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This is a no answer question!

Is your data so volatile (change this frequently)?

I load combo when I load the form. That kind of information is almost static. So the need of publishing your update mey be not so required! Don't forget that you can't broadcast your changes to other users!

If your data is very volatile, you may consider refreshing your combo systematically (when saving for example).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I'll add to this the fact that this is not a VB issue per se. Any UI or middle-layer using any sort of buffering can result in the same issue. In a langauge like VFP it is possible by not buffering, and setting the refresh and reprocess rates, but then you end up with very large amounts of database traffic. Hence, VFP like other languages increasingly is geared toward buffered states and/or delivery of subsets of data in the form of views or ADO recordsets.

In a VB app that I am working on right now, I have a "refresh pulldowns" menu item that requeries all combo boxes on all open forms (hidden or not). I told my users that they can choose this option if they have reason to believe the data have changed. (I am considering a routine in each form's Show event that will check how long it's been since that button was pressed, and it it has been over, say, half an hour, suggest that they refresh [the amount of time will be set by each user and stored in the registry]).